py-wrapt: updated to 2.4.1
2.4.1
Bugs Fixed
The C extension implementation of PartialCallableObjectProxy did not expose the bound positional and keyword arguments supplied when the proxy was created, whereas the pure Python implementation makes them available as the _self_args and _self_kwargs attributes. The C extension implementation now provides read only _self_args and _self_kwargs attributes so that both implementations behave the same.
inspect.signature() applied to a PartialCallableObjectProxy reported the full signature of the wrapped callable, including the parameters that the bound positional and keyword arguments already supply, whereas for functools.partial those parameters are removed. The proxy did not define __signature__, so inspect followed __wrapped__ back to the callable and reported its signature unchanged. The proxy now provides __signature__ on instances, in both the pure Python and C extension implementations, giving the same result as for an equivalent functools.partial, including a ValueError when more positional arguments are bound than the callable accepts.
This also affected wrapper functions used with FunctionWrapper and @wrapt.decorator. When a wrapped method is called via its class with the instance passed explicitly, the wrapper function receives a PartialCallableObjectProxy with the instance bound, and args without the instance. A wrapper which bound args and kwargs against inspect.signature(wrapped) would fail for such calls with a TypeError about a missing argument, while working for calls made via the instance. The reported signature now omits the bound instance so the binding succeeds.
The signature of a partial whose wrapped callable is itself an already bound method is still reported incorrectly, for reasons outside of the control of wrapt. See the “Known Issues” documentation for details.
The C extension intercepts the __module__ and __doc__ attributes by name in its attribute get and set slots so that they are forwarded to the wrapped object. The name was compared by identity against an interned string, which relied on the attribute name having been interned. Names originating from Python source code always are, but a name constructed at runtime, for example by string concatenation or by decoding, is not, and for such a name the interception was skipped. Getting the attribute then returned the value captured when the proxy was created rather than the current value on the wrapped object, and setting it stored the value on the proxy rather than the wrapped object. The comparison now falls back to comparing by value when the identity check fails, guarded by a length check so that the cost for non matching names is unchanged.
py-hypothesis: updated to 6.168.0
6.168.0 - 2026-09-08
datetimes() now generates “tricky” datetimes more often: values on or near daylight-saving and other utc-offset transitions of the drawn timezone - including imaginary wall times, and ambiguous ones with each value of fold - as well as times adjacent to leap seconds and to well-known datetimes like the millennium and the end of the signed 32-bit Unix epoch.
This release also fixes some rare internal errors, where an error raised partway through updating an internal cache - for example by a deeply recursive strategy raising RecursionError - could leave that cache corrupted.
www/webkit-gtk41: Revise comment about finding sqlite3
This is a comment-only change.
Somehow, cmake finds libraries in the buildlink path instead of the
real path. For most of them, the -L/rpath stuff ends up correct in
the built library. For sqlite3, for me on NetBSD 10 amd64 building
normally (not bulk), the buildlink path ends up in the final library.
Explain the problem better.
py-virtualenv: updated to 21.7.9
Bugfixes - 21.7.9
Replace dangling symlinks, including interpreter aliases, when recreating an environment. This prevents FileExistsError with --symlinks and writes outside the environment with --copies
Ignore malformed or unreadable virtualenv.ini files and report the error in the log and --help. Accept a UTF-8 byte order mark, as written by PowerShell 5 and older Notepad versions
py-tox: updated to 4.61.4
Bug fixes - 4.61.4
Shebang parsing now uses shlex, so a quoted interpreter path that contains spaces is kept as one argument when TOX_LIMITED_SHEBANG rewrites the invocation
Bug fixes - 4.61.3
A set_env environment file (file|.env) is now read as UTF-8 instead of the platform’s locale encoding, so non-ASCII values no longer arrive mangled on Windows
Preserve UNC and extended-length paths in Windows commands, including quoted paths
Normalize project and extra names in dependency-group self-references
Register factor labels and defaults for bare labeled dicts in env_list
py-filelock: updated to 3.32.6
3.32.6
fix(lease): reject a duration no marker can carry
fix(soft-rw): reject non-finite timing options
fix: preserve exception notes when copying and pickling
test(soft-rw): reuse existing test module
fix: respect ACL write access when the owner write bit is absent
Fix SoftReadWriteLock state lock timeout
py-diff-cover: added version 10.5.1
Automatically find diff lines that need test coverage. Also finds diff lines
that have violations (according to tools such as pycodestyle, pyflakes, flake8,
or pylint). This is used as a code quality metric during code reviews.
py-lazr.config: updated to 4.0.0
4.0.0
- Replace ``pkg_resources`` namespace with a PEP 420 native namespace.
- Consolidate packaging into a single ``pyproject.toml`` (remove ``setup.py``,
``setup.cfg``, and ``_version.py``).
- Standardize tox, Launchpad CI, pre-commit, and contributor documentation.
py-lazr.delegates: updated to 4.0.0
4.0.0
- Replace ``pkg_resources`` namespace with a PEP 420 native namespace.
- Consolidate packaging into a single ``pyproject.toml`` (remove ``setup.py``,
``setup.cfg``).
- Add support for Python 3.14.
- Update security auditing and linting.
- Standardize tox, Launchpad CI, pre-commit, and contributor documentation.
py-aio-pika: updated to 10.0.1
10.0.1
fix: use TypeVar for connect and connect_robust return types
10.0.0
Add aio-pika-batch to related projects
Update aiormq to the latest version 7
py-uv py-uv-build: updated to 0.12.13
0.12.13
Python
Add GraalPy 3.13.0
Enhancements
Verify hashes when downloading PEP 658 metadata sidecars
Preview features
Respect ty exclusions when uv check automatically selects members of a virtual workspace
Performance
Avoid full wheel downloads during resolution by reusing supported hashes from direct URL fragments when metadata is available separately
[14 lines not shown]
cargo-nextest: updated to 0.9.144
0.9.144
Changed
Failures while setting up run recording (for example, a store directory that cannot be created) are now always reported as warnings, and the test run continues without recording. Previously, only a store format version mismatch was treated as a warning, and other setup failures aborted the run. This makes setup consistent with recording finalization, which already never fails a run.
The "continue rerunning" hint printed when a rerun has outstanding tests is now only shown when the rerun was itself recorded, since cargo nextest run -R latest can only continue the chain in that case.
Fixed
Fixed the elapsed time shown in per-test running lines for tests that had been running for more than an hour. The minutes field was displayed as the total number of minutes rather than the minutes within the hour, producing output like [05:313:30].
When a cargo metadata or cargo build invocation fails, the error message now shows the full list of arguments that were passed to Cargo, including --color and --manifest-path. Previously, some arguments were omitted from the message.