fix(deps): update dependency trio to ^0.27.0 #264
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.26.2->^0.27.0Release Notes
python-trio/trio (trio)
v0.27.0Compare Source
Full Changelog: python-trio/trio@v0.26.2...v0.27.0
Breaking changes
trio.move_on_afterandtrio.fail_afterpreviously 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 usetrio.move_on_at(trio.current_time() + ...).flake8-async has a new rule to catch this, in case you're supporting older trio versions. See
ASYNC122. (https://github.com/python-trio/trio/issues/2512)Features
CancelScope.relative_deadlineandCancelScope.is_relativeadded, as well as arelative_deadlineparameter to__init__. This allows initializing scopes ahead of time, but where the specified relative deadline doesn't count down until the scope is entered. (https://github.com/python-trio/trio/issues/2512)trio.Lockandtrio.StrictFIFOLockwill now raisetrio.BrokenResourceErrorwhentrio.Lock.acquirewould previously stall due to the owner of the lock exiting without releasing the lock. (https://github.com/python-trio/trio/issues/3035)trio.move_on_at,trio.move_on_after,trio.fail_atandtrio.fail_afternow accept shield as a keyword argument. If specified, it provides an initial value for the~trio.CancelScope.shieldattribute of thetrio.CancelScopeobject created by the context manager. (https://github.com/python-trio/trio/issues/3052)trio.lowlevel.add_parking_lot_breakerandtrio.lowlevel.remove_parking_lot_breakerto allow creating custom lock/semaphore implementations that will break their underlying parking lot if a task exits unexpectedly.trio.lowlevel.ParkingLot.break_lotis also added, to allow breaking a parking lot intentionally. (https://github.com/python-trio/trio/issues/3081)Bugfixes
os.PathLikeobject. (https://github.com/python-trio/trio/issues/3041)trio.lowlevel.open_process's documentation to allow bytes. (https://github.com/python-trio/trio/issues/3076)trio.sleep_foreverto beNoReturn. (https://github.com/python-trio/trio/issues/3095)Improved documentation
statistics()andaclosemethods. (https://github.com/python-trio/trio/issues/3101)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.