* Add @trio.as_safe_channel, a wrapper that can be used to make async generators
safe. This will be the suggested fix for the flake8-async lint rule ASYNC900. (#3197)
* Allow trio to be a types.ModuleType and still have deprecated attributes. (#2135)
* Fixed socket module for some older systems which lack socket.AI_NUMERICSERV.
* Now trio works on legacy (pre-Lion) macOS. (#3133)
* Update type hints for trio.run_process and trio.lowlevel.open_process. (#3183)
* Don't mutate the global runner when MockClock is created. (#3205)
* Fix incorrect return type hint for Nursery.start(). (#3224)
* Update wording in documentation to more accurately reflect Trio's maturity. (#3216)
- Update BuildRequires from pyproject.toml
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-trio?expand=0&rev=56
- Update to 0.29.0
* Add trio.lowlevel.in_trio_run() and trio.lowlevel.in_trio_task() and document
the semantics (and differences) thereof. See the documentation. (#2757)
* If trio.testing.RaisesGroup does not get the expected exceptions it now raises
an AssertionError with a helpful message, instead of letting the raised exception/
group fall through. The raised exception is available in the __context__ of the
AssertionError and can be seen in the traceback. (#3145)
* Clear Trio’s cache of worker threads upon os.fork. (#2764)
* Stop using ctypes to mutate tracebacks for strict_exception_groups=False’s exception
collapsing. (#405)
* Fixed spelling error in Windows error code enum for ERROR_INVALID_PARAMETER. (#3166)
* Publicly re-export __version__ for type checking purposes. (#3186)
* The typing of trio.abc.HostnameResolver.getaddrinfo() has been corrected to match
that of the stdlib socket.getaddrinfo, which was updated in mypy 1.15 (via a typeshed
update) to include the possibility of tuple[int, bytes] for the sockaddr field of the
result. This happens in situations where Python was compiled with --disable-ipv6.
* Additionally, the static typing of trio.to_thread.run_sync(), trio.from_thread.run()
and trio.from_thread.run_sync() has been improved and should reflect the underlying
function being run. (#3201)
- Add sed command to remove shebangs from check_type_completeness.py and gen_exports.py
OBS-URL: https://build.opensuse.org/request/show/1250113
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-trio?expand=0&rev=54
- Update to 0.28.0
* :func:inspect.iscoroutinefunction and the like now give correct answers when
called on KI-protected functions.
* Rework KeyboardInterrupt protection to track code objects, rather than frames,
as protected or not. The new implementation no longer needs to access
frame.f_locals dictionaries, so it won't artificially extend the lifetime of
local variables. Since KeyboardInterrupt protection is now imposed statically
(when a protected function is defined) rather than each time the function runs,
its previously-noticeable performance overhead should now be near zero.
The lack of a call-time wrapper has some other benefits as well:
* :func:inspect.iscoroutinefunction and the like now give correct answers when
called on KI-protected functions.
* Calling a synchronous KI-protected function no longer pushes an additional stack
frame, so tracebacks are clearer.
* A synchronous KI-protected function invoked from C code (such as a weakref
finalizer) is now guaranteed to start executing; previously there would be a brief
window in which KeyboardInterrupt could be raised before the protection was
established.
* One minor drawback of the new approach is that multiple instances of the same
closure share a single KeyboardInterrupt protection state (because they share a
single code object). That means that if you apply
trio.lowlevel.enable_ki_protection to some of them
and not others, you won't get the protection semantics you asked for. See the
documentation of trio.lowlevel.enable_ki_protection
for more details and a workaround.
* Rework foreign async generator finalization to track async generator
ids rather than mutating ag_frame.f_locals. This fixes an issue
with the previous implementation: locals' lifetimes will no longer be
extended by materialization in the ag_frame.f_locals dictionary that
the previous finalization dispatcher logic needed to access to do its work.
OBS-URL: https://build.opensuse.org/request/show/1240795
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-trio?expand=0&rev=52
* :func:`trio.move_on_after` and :func:`trio.fail_after`
previously set the deadline relative to initialization time,
instead of more intuitively upon entering the context
manager. This might change timeouts if a program relied on
this behavior. If you want to restore previous behavior you
should instead use trio.move_on_at(trio.current_time() +
...). flake8-async has a new rule to catch this, in case
you're supporting older trio versions. See :ref:`ASYNC122`.
* :meth:`CancelScope.relative_deadline` and
:meth:`CancelScope.is_relative` added, as well as a
relative_deadline parameter to __init__. This allows
initializing scopes ahead of time, but where the specified
relative deadline doesn't count down until the scope is
entered.
* :class:`trio.Lock` and :class:`trio.StrictFIFOLock` will now
raise :exc:`trio.BrokenResourceError` when
:meth:`trio.Lock.acquire` would previously stall due to the
owner of the lock exiting without releasing the lock.
* trio.move_on_at, trio.move_on_after, trio.fail_at and
trio.fail_after now accept shield as a keyword argument. If
specified, it provides an initial value for the
~trio.CancelScope.shield attribute of the trio.CancelScope
object created by the context manager.
* Added :func:`trio.lowlevel.add_parking_lot_breaker` and
:func:`trio.lowlevel.remove_parking_lot_breaker` to allow
creating custom lock/semaphore implementations that will
break their underlying parking lot if a task exits
unexpectedly. :meth:`trio.lowlevel.ParkingLot.break_lot` is
also added, to allow breaking a parking lot intentionally.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-trio?expand=0&rev=51
- update to 0.26.2:
* Remove remaining hash usage and fix test configuration issue
that prevented it from being caught.
* Switched attrs usage off of hash, which is now deprecated.
* Use PyPI's Trusted Publishers to make releases.
* Added an interactive interpreter python -m trio. This makes
it easier to try things and experiment with trio in the a
Python repl. Use the await keyword without needing to call
trio.run() $ python -m trio Trio 0.21.0+dev, Python 3.10.6
Use "await" directly instead of "trio.run()". Type "help",
"copyright", "credits" or "license" for more information. >>>
import trio >>> await trio.sleep(1); print("hi") # prints
after one second hi See :ref:`interactive debugging` for
further detail. (#2972)
* :class:`trio.testing.RaisesGroup` can now catch an unwrapped
exception with unwrapped=True. This means that the behaviour
of :ref:`except* <except_star>` can be fully replicated in
combination with flatten_subgroups=True (formerly
strict=False). (#2989)
* Fixed a bug where :class:`trio.testing.RaisesGroup(...,
strict=False) <trio.testing.RaisesGroup>` would check the
number of exceptions in the raised ExceptionGroup before
flattening subgroups, leading to incorrectly failed matches.
It now properly supports end ($) regex markers in the match
message, by no longer including " (x sub-exceptions)" in the
string it matches against.
* Deprecated strict parameter from
:class:`trio.testing.RaisesGroup`, previous functionality of
strict=False is now in flatten_subgroups=True.
OBS-URL: https://build.opensuse.org/request/show/1199467
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-trio?expand=0&rev=19
* Remove remaining hash usage and fix test configuration issue
that prevented it from being caught.
* Switched attrs usage off of hash, which is now deprecated.
* Use PyPI's Trusted Publishers to make releases.
* Added an interactive interpreter python -m trio. This makes
it easier to try things and experiment with trio in the a
Python repl. Use the await keyword without needing to call
trio.run() $ python -m trio Trio 0.21.0+dev, Python 3.10.6
Use "await" directly instead of "trio.run()". Type "help",
"copyright", "credits" or "license" for more information. >>>
import trio >>> await trio.sleep(1); print("hi") # prints
after one second hi See :ref:`interactive debugging` for
further detail. (#2972)
* :class:`trio.testing.RaisesGroup` can now catch an unwrapped
exception with unwrapped=True. This means that the behaviour
of :ref:`except* <except_star>` can be fully replicated in
combination with flatten_subgroups=True (formerly
strict=False). (#2989)
* Fixed a bug where :class:`trio.testing.RaisesGroup(...,
strict=False) <trio.testing.RaisesGroup>` would check the
number of exceptions in the raised ExceptionGroup before
flattening subgroups, leading to incorrectly failed matches.
It now properly supports end ($) regex markers in the match
message, by no longer including " (x sub-exceptions)" in the
string it matches against.
* Deprecated strict parameter from
:class:`trio.testing.RaisesGroup`, previous functionality of
strict=False is now in flatten_subgroups=True.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-trio?expand=0&rev=49
2024-09-08 15:07:35 +00:00
5 changed files with 39 additions and 32 deletions
oid sha256:f71d551ccaa79d0cb73017a33ef3264fde8335728eb4c6391451fe5d253a9d5b
size 605825
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
