Release: https://pypi.org/pypi/pyflakes/3.0.0
Homepage: https://github.com/PyCQA/pyflakes
Diff: https://github.com/PyCQA/pyflakes/compare/2.5.0...3.0.0
Stubsabot analysis of the diff between the two releases:
- 0 public Python files have been added.
- 0 files included in typeshed's stubs have been deleted.
- 4 files included in typeshed's stubs have been modified or renamed: `pyflakes/__init__.py`, `pyflakes/api.py`, `pyflakes/checker.py`, `pyflakes/messages.py`.
- Total lines of Python code added: 80.
- Total lines of Python code deleted: 446.
Co-authored-by: AlexWaygood <alex.waygood@gmail.com>
We're about to get a daily test failure with 63 stubtest errors (see the Ubuntu stubtest failure in #9187) due to the release of redis-py 4.3.5, and I'd rather that didn't happen.
Release: https://pypi.org/pypi/flake8-rst-docstrings/0.3.0
Homepage: https://github.com/peterjc/flake8-rst-docstrings
Diff: https://github.com/peterjc/flake8-rst-docstrings/compare/v0.2.7...v0.3.0
Stubsabot analysis of the diff between the two releases:
- 2 public Python files have been added: `tests/RST214/plurals.py`, `tests/RST215/plurals.py`.
- 0 files included in typeshed's stubs have been deleted.
- 1 file included in typeshed's stubs has been modified or renamed: `flake8_rst_docstrings.py`.
- Total lines of Python code added: 38.
- Total lines of Python code deleted: 54.
If stubtest fails for this PR:
- Leave this PR open (as a reminder, and to prevent stubsabot from opening another PR)
- Fix stubtest failures in another PR, then close this PR
Note that you will need to close and re-open the PR in order to trigger CI
Co-authored-by: stubsabot <>
- Change the return type of create_connection, start_tls,
connect_accepted_socket, create_unix_connection to Transport
rather than BaseTransport (closes#9199).
- Change the return type of create_datagram_endpoint to
DatagramTransport rather than BaseTransport.
- Change the argument of sendfile to WriteTransport rather than
BaseTransport.
I considered also changing the argument of start_tls to Transport, but
I think that will give false positives for code that implements a custom
transport class that inherits from both ReadTransport and WriteTransport
but not from Transport, and I'm not sure if typing has a way to express
an intersection of types. Since users are not normally expected to
implement transports that may be overthinking things.
