| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upgrade to release 0.27.0:
- trio.move_on_after and trio.fail_after previously set the deadline
relative to initialization time, instead of more intuitively upon
entering the context manager.
- CancelScope.relative_deadline and 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
- trio.Lock and trio.StrictFIFOLock will now raise
trio.BrokenResourceError when 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 trio.lowlevel.add_parking_lot_breaker and
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.
trio.lowlevel.ParkingLot.break_lot is also added, to allow
breaking a parking lot intentionally
- Allow sockets to bind any os.PathLike object
- Update trio.lowlevel.open_process's documentation to allow bytes
- Update trio.sleep_forever to be NoReturn
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
