Release: https://pypi.org/pypi/Flask-Cors/4.0.0
Homepage: https://github.com/corydolphin/flask-cors
Diff: https://github.com/corydolphin/flask-cors/compare/3.0.10...v4.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.
- 5 files included in typeshed's stubs have been modified or renamed: `flask_cors/__init__.py`, `flask_cors/core.py`, `flask_cors/decorator.py`, `flask_cors/extension.py`, `flask_cors/version.py`.
- Total lines of Python code added: 50.
- Total lines of Python code deleted: 41.
* [stubsabot] Bump pyinstaller to 5.13.*
Release: https://pypi.org/pypi/pyinstaller/5.13.0
Homepage: https://www.pyinstaller.org/
Diff: https://github.com/pyinstaller/pyinstaller/compare/v5.12.0...v5.13.0
Stubsabot analysis of the diff between the two releases:
- 1 public Python file has been added: `PyInstaller/hooks/pre_safe_import_module/hook-distutils.py`.
- 0 files included in typeshed's stubs have been deleted.
- 4 files included in typeshed's stubs have been modified or renamed: `PyInstaller/__init__.py`, `PyInstaller/building/api.py`, `PyInstaller/building/build_main.py`, `PyInstaller/compat.py`.
- Total lines of Python code added: 962.
- Total lines of Python code deleted: 648.
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
* Update compat.pyi
---------
Co-authored-by: stubsabot <>
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
Also require `bytes` for all `hash_id`s for consistency, even
if some methods might work with other types as well. But
using other types might hint at some inconsistent type
usage and be a source of possible bugs.
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
Release: https://pypi.org/pypi/hdbcli/2.17.14
Homepage: https://www.sap.com/
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 <>
Release: https://pypi.org/pypi/pyinstaller/5.12.0
Homepage: https://www.pyinstaller.org/
Diff: https://github.com/pyinstaller/pyinstaller/compare/v5.11.0...v5.12.0
Stubsabot analysis of the diff between the two releases:
- 2 public Python files have been added: `tests/functional/scripts/pyi_lazy_import.py`, `tests/functional/test_import_lazy_loader.py`.
- 0 files included in typeshed's stubs have been deleted.
- 6 files included in typeshed's stubs have been modified or renamed: `PyInstaller/__init__.py`, `PyInstaller/building/build_main.py`, `PyInstaller/building/splash.py`, `PyInstaller/compat.py`, `PyInstaller/lib/modulegraph/modulegraph.py`, `PyInstaller/utils/win32/versioninfo.py`.
- Total lines of Python code added: 647.
- Total lines of Python code deleted: 887.
And make many attributes read-only. The primary entry point to this module in `IniFile` (or its subclass
`AppIniFile`). Since the config file is read (from `filename`) and
parsed (using the `dialect`) in the `IniFile` constructor, modifying
attributes like `IniFile.filename` or `IniFile.dialect` after
construction is likely to cause problems.
Release: https://pypi.org/pypi/flake8-bugbear/23.6.5
Homepage: https://github.com/PyCQA/flake8-bugbear
Changelog: https://github.com/PyCQA/flake8-bugbear#change-log
Diff: https://github.com/PyCQA/flake8-bugbear/compare/23.5.9...23.6.5
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.
- 1 file included in typeshed's stubs has been modified or renamed: `bugbear.py`.
- Total lines of Python code added: 31.
- Total lines of Python code deleted: 18.
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 <>
