[orm] [usecase] Added support for the PEP 695TypeAliasType construct as well as the
python 3.12 native type keyword to work with ORM Annotated Declarative
form when using these constructs to link to a PEP 593Annotated
container, allowing the resolution of the Annotated to proceed when
these constructs are used in a _orm.Mapped typing container.
[orm] [bug] Fixed Declarative issue where typing a relationship using
_orm.Relationship rather than _orm.Mapped would
inadvertently pull in the "dynamic" relationship loader strategy for that
attribute.
[orm] [bug] Fixed issue in ORM annotated declarative where using
_orm.mapped_column() with an _orm.mapped_column.index
or _orm.mapped_column.unique setting of False would be
overridden by an incoming Annotated element that featured that
parameter set to True, even though the immediate
_orm.mapped_column() element is more specific and should take
precedence. The logic to reconcile the booleans has been enhanced to
accommodate a local value of False as still taking precedence over an
incoming True value from the annotated element.
[orm] [bug] [regression] Fixed regression from version 2.0.28 caused by the fix for #11085
where the newer method of adjusting post-cache bound parameter values would
interefere with the implementation for the _orm.subqueryload() loader
option, which has some more legacy patterns in use internally, when
the additional loader criteria feature were used with this loader option.
[engine] [bug] Fixed issue in engine_insertmanyvalues feature where using a primary
key column with an "inline execute" default generator such as an explicit
Sequence with an explcit schema name, while at the same time
using the
_engine.Connection.execution_options.schema_translate_map
This release is a milestone: it fixes Black's first CVE security vulnerability. If you
run Black on untrusted input, or if you habitually put thousands of leading tab
characters in your docstrings, you are strongly encouraged to upgrade immediately to fix
CVE-2024-21503.
This release also fixes a bug in Black's AST safety check that allowed Black to make
incorrect changes to certain f-strings that are valid in Python 3.12 and higher.
Stable style
Don't move comments along with delimiters, which could cause crashes (#4248)
Strengthen AST safety check to catch more unsafe changes to strings. Previous versions
of Black would incorrectly format the contents of certain unusual f-strings containing
nested strings with the same quote type. Now, Black will crash on such strings until
support for the new f-string syntax is implemented. (#4270)
Fix a bug where line-ranges exceeding the last code line would not work as expected
(#4273)
Performance
Fix catastrophic performance on docstrings that contain large numbers of leading tab
characters. This fixes
CVE-2024-21503.
(#4278)
Documentation
Note what happens when --check is used with --quiet (#4236)
24.2.0
Stable style
Fixed a bug where comments where mistakenly removed along with redundant parentheses
(#4218)
Preview style
Move the hug_parens_with_braces_and_square_brackets feature to the unstable style
due to an outstanding crash and proposed formatting tweaks (#4198)
Fixed a bug where base expressions caused inconsistent formatting of ** in tenary
expression (#4154)
Checking for newline before adding one on docstring that is almost at the line limit
(#4185)
Remove redundant parentheses in case statement if guards (#4214).
This release is a milestone: it fixes Black's first CVE security vulnerability. If you
run Black on untrusted input, or if you habitually put thousands of leading tab
characters in your docstrings, you are strongly encouraged to upgrade immediately to fix
CVE-2024-21503.
This release also fixes a bug in Black's AST safety check that allowed Black to make
incorrect changes to certain f-strings that are valid in Python 3.12 and higher.
Stable style
Don't move comments along with delimiters, which could cause crashes (#4248)
Strengthen AST safety check to catch more unsafe changes to strings. Previous versions
of Black would incorrectly format the contents of certain unusual f-strings containing
nested strings with the same quote type. Now, Black will crash on such strings until
support for the new f-string syntax is implemented. (#4270)
Fix a bug where line-ranges exceeding the last code line would not work as expected
(#4273)
Performance
Fix catastrophic performance on docstrings that contain large numbers of leading tab
characters. This fixes
CVE-2024-21503.
(#4278)
Documentation
Note what happens when --check is used with --quiet (#4236)
24.2.0
Stable style
Fixed a bug where comments where mistakenly removed along with redundant parentheses
(#4218)
Preview style
Move the hug_parens_with_braces_and_square_brackets feature to the unstable style
due to an outstanding crash and proposed formatting tweaks (#4198)
Fixed a bug where base expressions caused inconsistent formatting of ** in tenary
expression (#4154)
Checking for newline before adding one on docstring that is almost at the line limit
(#4185)
Remove redundant parentheses in case statement if guards (#4214).
We’ve just uploaded mypy 1.9 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:
python3 -m pip install -U mypy
You can read the full documentation for this release on Read the Docs.
Breaking Changes
Because the version of typeshed we use in mypy 1.9 doesn't support 3.7, neither does mypy 1.9. (Jared Hance, PR 16883)
We are planning to enable
local partial types (enabled via the
--local-partial-types flag) later this year by default. This change
was announced years ago, but now it's finally happening. This is a
major backward-incompatible change, so we'll probably include it as
part of the upcoming mypy 2.0 release. This makes daemon and
non-daemon mypy runs have the same behavior by default.
Local partial types can also be enabled in the mypy config file:
local_partial_types = True
We are looking at providing a tool to make it easier to migrate
projects to use --local-partial-types, but it's not yet clear whether
this is practical. The migration usually involves adding some
explicit type annotations to module-level and class-level variables.
Basic Support for Type Parameter Defaults (PEP 696)
This release contains new experimental support for type parameter
defaults (PEP 696). Please try it
out! This feature was contributed by Marc Mueller.
Since this feature will be officially introduced in the next Python
feature release (3.13), you will need to import TypeVar, ParamSpec
or TypeVarTuple from typing_extensions to use defaults for now.
This example adapted from the PEP defines a default for BotT:
from typing import Generic
from typing_extensions import TypeVar
* Do specifier matching correctly when the specifier contains an epoch number
and has more components than the version (:issue:`683`)
* Support the experimental ``--disable-gil`` builds in packaging.tags
(:issue:`727`)
* BREAKING: Make optional ``metadata.Metadata`` attributes default to ``None`` (:issue:`733`)
* Fix errors when trying to access the ``description_content_type``, ``keywords``,
and ``requires_python`` attributes on ``metadata.Metadata`` when those values
have not been provided (:issue:`733`)
* Fix a bug preventing the use of the built in ``ExceptionGroup`` on versions of
Python that support it (:issue:`725`)
- Fix bug that now means the number of parameters cam be as high as an unsigned 16 bit
integer will go.
Version 1.30.4, 2024-01-03
Add support for more range and multirange types.
Make the Connection.parameter_statuses property a dict rather than a dequeue.
Version 1.30.3, 2023-10-31
- Fix problem with PG date overflowing Python types. Now we return the ``str`` we got from the
server if we can't parse it.
Version 1.30.2, 2023-09-17
Bug fix where dollar-quoted string constants weren't supported.
Version 1.30.1, 2023-07-29
- There was a problem uploading the previous version (1.30.0) to PyPI because the
markup of the README.rst was invalid. There's now a step in the automated tests to
check for this.
Version 1.30.0, 2023-07-27
Remove support for Python 3.7
Add a sock keyword parameter for creating a connection from a pre-configured
socket.
This release is not a usual bug fix release -- it contains features and improvements, being a follow up
to 8.1.0, which has been yanked from PyPI.
:::
Features
#11475: Added the new consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting to False.
If set to True, pytest will attempt to identify modules that are part of namespace packages when importing modules.
#11653: Added the new verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.
See Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.
Improvements
#10865: pytest.warns{.interpreted-text role="func"} now validates that warnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.
Currently in Python it is possible to use other types, however this causes an exception when warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](python/cpython#103577) for a discussion).
While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using --override-ini for paths in invocations without a configuration file defined, the current working directory is used
as the relative directory.
Previoulsy this would raise an AssertionError{.interpreted-text role="class"}.
#11475: --import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.
This means that installed packages will be imported under their canonical name if possible first, for example app.core.models, instead of having the module name always be derived from their path (for example .env310.lib.site_packages.app.core.models).
#11801: Added the iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes.
It is similar to listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.
#11850: Added support for sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.
#11962: In case no other suitable candidates for configuration file are found, a pyproject.toml (even without a [tool.pytest.ini_options] table) will be considered as the configuration file and define the rootdir.
#11978: Add --log-file-mode option to the logging plugin, enabling appending to log-files. This option accepts either "w" or "a" and defaults to "w".
Previously, the mode was hard-coded to be "w" which truncates the file before logging.
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
Fix typing errors with recent versions of mypy #769
Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
Fix typing errors with recent versions of mypy #769
Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
Fix typing errors with recent versions of mypy #769
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
pytest-asyncio 0.23.4
0.23.4 (2024-01-28)
pytest-asyncio no longer imports additional, unrelated packages during test collection #729
Addresses further issues that caused an internal pytest error during test collection
pytest-asyncio no longer imports additional, unrelated packages during test collection #729
Addresses further issues that caused an internal pytest error during test collection
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
... (truncated)
Commits
c34da04 [docs] Mentioned pytest 8.2 compatibility fix in changelog.
143f745 Fix compatibility with pytest 8.2 FixtureDef.unittest removal
Bumps the all-dependencies group with 14 updates:
2.0.232.0.292.0.17012298372.0.170890739123.12.124.3.07.0.17.1.01.8.01.9.02023.4.222024.3.223.224.01.30.31.30.57.4.38.1.10.23.20.23.62.2.02.2.14.1.05.0.03.0.03.1.167.8.069.2.0Updates
sqlalchemyfrom 2.0.23 to 2.0.29Release notes
Sourced from sqlalchemy's releases.
... (truncated)
Commits
Updates
sqlakeysetfrom 2.0.1701229837 to 2.0.1708907391Commits
Updates
blackfrom 23.12.1 to 24.3.0Release notes
Sourced from black's releases.
... (truncated)
Changelog
Sourced from black's changelog.
... (truncated)
Commits
552baf8Prepare release 24.3.0 (#4279)f000936Fix catastrophic performance in lines_with_leading_tabs_expanded() (#4278)7b5a657Fix --line-ranges behavior when ranges are at EOF (#4273)1abcffcUse regex where we ignore case on windows (#4252)719e674Fix 4227: Improve documentation for --quiet --check (#4236)e5510afupdate plugin url for Thonny (#4259)6af7d11Fix AST safety check false negative (#4270)f03ee11Ensureblib2to3.pygramis initialized before use (#4224)e4bfedbfix: Don't move comments while splitting delimiters (#4248)d0287e1Make trailing comma logic more concise (#4202)Updates
importlib-metadatafrom 7.0.1 to 7.1.0Changelog
Sourced from importlib-metadata's changelog.
Commits
f5d6b5fFinalize2ef3b5fMerge commit '1711b2c198'1711b2cNeed to include names from test.support for py312 compat.47b14acMake MetadataPathFinder.find_distributions a classmethod for consistency with...adc4b12Ensure tests do not leak references in sys.modules.07d894dCopy backport of isolated_modules from importlib_resources.e30a16dConsolidated test support logic in jaraco.test.cpython.41ca039Moved compatibility tests to the compat package, as they're not included in C...5950f43Remove legacy logic for Python 3.7.ffa719bMoved compatibility module to compat package.Updates
mypyfrom 1.8.0 to 1.9.0Changelog
Sourced from mypy's changelog.
... (truncated)
Commits
5ff46f8Remove +dev.155909a[Release 1.9] Unsupport targetting 3.7. (#16883) (#16900)6615cab[Release 1.9] Stubtest: ignore a new protocol dunder (#16895) (#16899)b956e6astubtest: Private parameters can be omitted (#16507)ede0b20Bump ruff to 0.2.0 (#16870)7bdd61fstubgen: Fix crash on star unpack of TypeVarTuple (#16869)8c2ef9dUpdate hashes in sync-typeshed.py following recent typeshed sync0dd4b6fRevert use ofParamSpecforfunctools.wrapsdd12a2dRevert typeshed ctypes changed132999Revert sum literal integer change (#13961)Updates
noxfrom 2023.4.22 to 2024.3.2Release notes
Sourced from nox's releases.
... (truncated)
Changelog
Sourced from nox's changelog.
... (truncated)
Commits
4c8e891Release 2024.03.02 (#789)d862350feat: venv backend fallback (#787)1c6af24fix: warn user when first argument to session.run is a list (#786)d59e1acfix: rebuild env if making an incompatible change (#781)ff259cechore(deps): bump the actions group with 2 updates (#784)93bacbdAllow configuringdefault_venv_backendwith an environment variable (#780)5a097cdfeat: support for reuse_venv option (#730)55e09cdfix: always pull versions from metadata (#782)c248a76chore: cleanup Ruff a bit (#783)1fe4437feat: add a uv backend (#762)Updates
packagingfrom 23.2 to 24.0Release notes
Sourced from packaging's releases.
Changelog
Sourced from packaging's changelog.
Commits
7a983f7Bump for release4d85340Add riscv64 as a supported manylinux architecture (#751)4dce761Apply some ruff suggestions (#772)57a6a7fAppply some bugbear suggestions (#761)7bcd6d8Apply some refurb suggestions (#763)d0067e9[StepSecurity] ci: Harden GitHub Actions (#1) (#758)eae70ddfeat: Create dependabot.yml (#757)241bb35Update URLs (#764)7698237Remove coverage ignore for non-existent file (#752)b271d2bReplace PEP references with PUG links (#750)Updates
pg8000from 1.30.3 to 1.30.5Changelog
Sourced from pg8000's changelog.
... (truncated)
Commits
bf16ea5Prepare for new release4ef917eUse unsigned 16 bit integer in protocol7d0cddeMove sections from readme to a separate pagef6f416cPrepare for new release8adb556Add support for more range and multirange types796cd01Make Connection.parameter_statuses a dicta93944eFix doctest for PostgreSQL 15+433e01fFix doctest problem with IDENTIFY_SYSTEM commanda2dc1e8Fix copy tests for PostgreSQL 16c662f40PostgreSQL versions: add 16, drop 11Updates
pytestfrom 7.4.3 to 8.1.1Release notes
Sourced from pytest's releases.
... (truncated)
Commits
81653eeAdjust changelog manually for 8.1.1e60b4b9Prepare release version 8.1.115fbe57[8.1.x] Revert legacy path removals (#12093)86c3aab[8.1.x] Do not import duplicated modules with --importmode=importlib (#12077)5b82b0c[8.1.x] Yank version 8.1.0 (#12076)0a53681Merge pull request #12054 from pytest-dev/release-8.1.0b9a167fPrepare release version 8.1.000043f7Merge pull request #12038 from bluetech/fixtures-rm-arg2indexf4e1025Merge pull request #12048 from bluetech/fixture-teardown-excgroup43492f5Merge pull request #12051 from jakkdl/test_debugging_pythonbreakpointUpdates
pytest-asynciofrom 0.23.2 to 0.23.6Release notes
Sourced from pytest-asyncio's releases.
... (truncated)
Commits
c34da04[docs] Mentioned pytest 8.2 compatibility fix in changelog.143f745Fix compatibility with pytest 8.2 FixtureDef.unittest removal13d4b79Remove unused function_removesuffixcdd2c49UseFixtureRequestinstead ofSubRequestc3429faBuild(deps): Bump packaging from 23.2 to 24.0 in /dependencies/docs5f2338dBuild(deps): Bump pypa/gh-action-pypi-publish from 1.8.12 to 1.8.14726c6e0Build(deps): Bump coverage from 7.4.3 to 7.4.4 in /dependencies/default8bd8288Build(deps): Bump pytest from 8.0.2 to 8.1.1 in /dependencies/defaultCodSpeed Performance Report
Merging #143 will not alter performance
Comparing
dependabot/pip/all-dependencies-9f8fb93559(5dadde6) withmain(ba0dceb)Summary
✅ 1untouched benchmarksSuperseded by #146.