| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Drop support for Python 3.7 (#2137) | Marc Mueller | 2023-04-23 | 1 | -88/+45 |
| | | |||||
| * | [PyCQA migration] Upgrade links to the repositories in code and doc | Pierre Sassoulas | 2023-03-29 | 1 | -2/+2 |
| | | |||||
| * | Initial pass with ``pydocstringformatter`` | Daniël van Noord | 2023-01-09 | 1 | -1/+1 |
| | | |||||
| * | Misc type stuff (#1888) | Nick Drozd | 2022-12-15 | 1 | -0/+2 |
| | | |||||
| * | Update typing for Python 3.7 (1) (#1555) | Marc Mueller | 2022-05-13 | 1 | -14/+16 |
| | | |||||
| * | Add annotations for ParserModule (#1526) | Marc Mueller | 2022-04-23 | 1 | -23/+30 |
| | | |||||
| * | Simplify hard to maintain copyright notice (#1441) | Pierre Sassoulas | 2022-03-12 | 1 | -0/+4 |
| | | | | | | | | | | | | | | | * Simplify hard to maintain copyright notice git is the source of truth for the copyright, copyrite (the tool) was taking exponentially longer with each release, and it's polluting the code with sometime as much as 50 lines of names. * Add a pre-commit hook to check the copyright notice * Fix the existing file so they have a notice * Fix the spacing after the copyright notice * Add a script to generate the CONTRIBUTORS.txt Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com> | ||||
| * | Add typing to ``_ast`` (#1296) | Daniël van Noord | 2021-12-16 | 1 | -14/+11 |
| | | |||||
| * | Rename non obvious PY3X constant to PY3X_PLUS | Pierre Sassoulas | 2021-06-21 | 1 | -3/+3 |
| | | | | | See https://github.com/PyCQA/astroid/pull/1069\#issuecomment-865206120 | ||||
| * | Rename astroid.constants to astroid.const | Pierre Sassoulas | 2021-06-19 | 1 | -1/+1 |
| | | | | | See https://github.com/PyCQA/astroid/pull/1045\#discussion_r654572722 | ||||
| * | Proper return type for _contexts_from_module | Pierre Sassoulas | 2021-06-19 | 1 | -1/+1 |
| | | | | | See https://github.com/PyCQA/astroid/pull/1045\#discussion_r654570889 | ||||
| * | Create a permanent enum for Context instead of deleting the class | Pierre Sassoulas | 2021-06-19 | 1 | -8/+7 |
| | | |||||
| * | Create a astroid.constants.py to avoid circular imports | Pierre Sassoulas | 2021-06-17 | 1 | -1/+1 |
| | | | | | And add PY3X type constants in it. | ||||
| * | Fix F811 redefinition of unused '_ast_py3' | Pierre Sassoulas | 2021-05-01 | 1 | -2/+1 |
| | | |||||
| * | Add an isort configuration in setup.cfg and apply it | Pierre Sassoulas | 2021-04-19 | 1 | -1/+1 |
| | | | | | Except on astroid/__init__.py because of circular imports | ||||
| * | Restructure the AST parsing heuristic to always pick the same module | Claudiu Popa | 2020-04-29 | 1 | -23/+100 |
| | | | | | | | | | | | | | | | When a file contained a misplaced type annotation, we were retrying the parsing without type comments support. That second parsing was using the builtin ast module, but the rest of the tree utilities (the builder and rebuilder) were not aware of the new parsing module that was used to build the AST nodes a second time. This commit moves the logic of picking the parsing module and the corresponding AST node mapping in a single place, which can be used by both the builder and the rebuilder. Close PyCQA/pylint#3540 Close #773 | ||||
| * | Retry parsing a module that has invalid type comments | Claudiu Popa | 2019-11-26 | 1 | -5/+10 |
| | | | | | | | | | It is possible for a module to use comments that might be interpreted as type comments by the `ast` library. We do not want to completely crash on those invalid type comments. Close #708 | ||||
| * | Obtain type comments on Python 3.8 by passing type_comments=True to the ↵ | Claudiu Popa | 2019-07-10 | 1 | -2/+5 |
| | | | | | parse function | ||||
| * | Fallback to the builtin ast on Python 3.8 when typed_ast is not available | Claudiu Popa | 2019-07-09 | 1 | -0/+6 |
| | | |||||
| * | When picking the parse function, make sure to parse with the right minor versionastroid-2.2.0 | Claudiu Popa | 2019-02-27 | 1 | -1/+7 |
| | | | | | | Until now we were parsing with the default 3.6 with typed_ast, which does not make sense for Python 3.5 and 3.4 | ||||
| * | Update to typed-ast 1.3 and drop the Python 3.7 restriction | Claudiu Popa | 2019-02-19 | 1 | -5/+0 |
| | | | | | Close #646 | ||||
| * | Initial formatting of astroid | Claudiu Popa | 2018-10-02 | 1 | -7/+3 |
| | | |||||
| * | Don't use typed_ast is the Python version is 3.7+ | Claudiu Popa | 2018-06-09 | 1 | -0/+5 |
| | | | | | | typed_ast doesn't fully support the complete syntax of 3.7 which will result in SyntaxErrors when building trees with 3.7 specific syntax. | ||||
| * | Add support for parsing function type comments | Claudiu Popa | 2018-06-04 | 1 | -0/+17 |
| | | | | | | | This commit exposes two new attributes to the FunctionDef nodes, type_comment_args respectively type_comment_annotations. These two attributes hold the type annotations provided via type comments. | ||||
| * | Add support for type comments (#548) | Claudiu Popa | 2018-05-23 | 1 | -0/+21 |
 |
index : delta/python-packages/astroid-git.git | |
| github.com: PyCQA/astroid.git |
| summaryrefslogtreecommitdiff |