| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
un-executed, white space, time stamp.
|
|
|
|
| |
This was a holdover from Python 2 days.
|
| |
|
|
|
|
|
|
| |
Revert "refactor: we no longer need to treat 'class' lines specially"
This reverts commit 79f9f4575321fafc2ef770e3255f874db3d4b037.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before these changes, these violations happened:
```
lint run-test: commands[6] | python -m pylint --notes= coverage tests doc ci igor.py setup.py __main__.py
************* Module coverage.parser
coverage/parser.py:1290 I: Useless suppression of 'too-many-function-args' (useless-suppression)
************* Module ci.download_gha_artifacts
ci/download_gha_artifacts.py:18 W: Missing timeout argument for method 'requests.get' can cause your program to hang indefinitely (missing-timeout)
ci/download_gha_artifacts.py:54 W: Missing timeout argument for method 'requests.get' can cause your program to hang indefinitely (missing-timeout)
************* Module ci.trigger_build_kits
ci/trigger_build_kits.py:21 W: Missing timeout argument for method 'requests.post' can cause your program to hang indefinitely (missing-timeout)
************* Module ci.github_releases
ci/github_releases.py:138 E: Too many positional arguments for function call (too-many-function-args)
ci/github_releases.py:138 I: Useless suppression of 'no-value-for-parameter' (useless-suppression)
************* Module ci.comment_on_fixes
ci/comment_on_fixes.py:30 W: Missing timeout argument for method 'requests.get' can cause your program to hang indefinitely (missing-timeout)
ci/comment_on_fixes.py:37 W: Missing timeout argument for method 'requests.get' can cause your program to hang indefinitely (missing-timeout)
ci/comment_on_fixes.py:49 W: Missing timeout argument for method 'requests.post' can cause your program to hang indefinitely (missing-timeout)
************* Module ci.parse_relnotes
ci/parse_relnotes.py:126 E: Too many positional arguments for function call (too-many-function-args)
ci/parse_relnotes.py:126 I: Useless suppression of 'no-value-for-parameter' (useless-suppression)
```
|
|
|
|
|
| |
CPython added these lines in
https://github.com/python/cpython/commit/1bfe83a114da3939c00746fc44dc5da7f56f525f
|
|
|
|
|
| |
Wrote this bug for pylint, because I shouldn't have to add a pragma:
https://github.com/PyCQA/pylint/issues/6592
|
| |
|
| |
|
| |
|
|
|
|
| |
See: https://bugs.python.org/issue46234
|
|
|
|
| |
... and make some of them private.
|
|
|
|
|
| |
Originally, this tokenizing code was paired with bytecode analysis. But now we
use AST instead, so class lines don't need to be handled differently.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
missing branches. #1205
|
|
|
|
|
| |
File names should not be rendered with !r, since on Windows that will
produce double backslashes, which only confuses people.
|
| |
|
| |
|
|
|
|
|
|
| |
This makes exceptions report their causes correctly, as "The above exception was
the direct cause of the following exception" instead of "During handling of the
above exception, another exception occurred."
|
| |
|
|
|
|
| |
This need 3.10.0b3 (not yet released) to fully pass.
|
|
|
|
|
| |
It was only ever used once per object, so just make the ByteParser when
we need it.
|
|
|
|
|
|
|
|
|
| |
Every statement-level ast node should be tested. Annotated assignment
was missing.
Also, we don't need "exec" anymore, that was only for Python 2.
And: this is the 1000th test!
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gone are:
- iitems
- litems
- iternext
- to_bytes
- to_string
- binary_bytes
- byte_to_int
- bytes_to_ints
- BUILTINS
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removed were:
- StringIO
- configparser
- string_class
- unicode_class
- range
- zip_longest
- get_thread_id
- path_types
- shlex_quote
- reprlib
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The conditionals are now getting unwieldy, perhaps we can simplify them
in the future?
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We've long remapped line numbers to the first line of a multi-line
statement. But exit line numbers (negative numbers) were not remapped.
This meant we were needlessly chasing weirdnesses in implementations.
But the actual results of running coverage always remapped results to
the first line, so there's no point in tracking the unmapped line
numbers in our tests.
|
| |
|
| |
|
| |
|
| |
|