- update to 0.27.0:
  * :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.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- 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.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to 0.25.1:
  * Fix crash when importing trio in embedded Python on Windows,
    and other installs that remove docstrings.
  * MultiError has been fully removed, and all relevant trio
  * The strict_exception_groups parameter now defaults to True
  * Add trio.testing.wait_all_threads_completed, which blocks
  * Path is now a subclass of pathlib.PurePath, allowing it to

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to 0.25.0
  * New helper classes: RaisesGroup and Matcher.
  * MultiError has been fully removed, and all relevant trio 
    functions now raise ExceptionGroups instead.
  * The strict_exception_groups parameter now defaults to True 
    in trio.run and trio.lowlevel.start_guest_run.
  * Add trio.testing.wait_all_threads_completed, which blocks 
    until no threads are running tasks.
  * Path is now a subclass of pathlib.PurePath, allowing it to 
    interoperate with other standard pathlib types.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- We don't need isort for the tests: Avoid it for Ring1
- Clean dependencies

• Files Changed
• Browse Source

- Run tests with --pyargs

• Files Changed
• Browse Source

- update to 0.23.2:
  * TypeVarTuple is now used to fully type
    :meth:`nursery.start_soon() <trio.Nursery.start_soon>`,
    :func:`trio.run()`, :func:`trio.to_thread.run_sync()`, and
    other similar functions accepting (func, *args). This means
    type checkers will be able to verify types are used
    correctly. :meth:`nursery.start() <trio.Nursery.start>` is
    not fully typed yet however. (#2881)
  * Make pyright recognize :func:`open_memory_channel` as
    generic. (#2873)
    backlink Unknown interpreted text role "func".
  * Make pyright recognize :func:`open_memory_channel` as
    generic.
  * Unknown interpreted text role "func".
  * Moved the metadata into PEP 621-compliant
    :file:`pyproject.toml`. (#2860)

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- update to 0.23.1:
  * Don't crash on import in Anaconda interpreters.
  * Add type hints.
  * When exiting a nursery block, the parent task always waits
    for child tasks to exit. This wait cannot be cancelled. However,
    previously, if you tried to cancel it, it *would* inject a
    `Cancelled` exception, even though it wasn't cancelled.
    Most users probably never noticed either way, but injecting a
    `Cancelled` here is not really useful, and in some rare cases
    caused confusion or problems, so Trio no longer does that.
  * If called from a thread spawned by `trio.to_thread.run_sync`,
    `trio.from_thread.run` and `trio.from_thread.run_sync` now
    reuse the task and cancellation status of the host task;
  * this means that context variables and cancel scopes naturally
    propagate 'through' threads spawned by Trio. You can also use
    `trio.from_thread.check_cancelled`
    to efficiently check for cancellation without reentering the
    Trio thread.
  * :func:`trio.lowlevel.start_guest_run` now does a bit more
    setup of the guest run before it returns to its caller,
    so that the caller can immediately make calls to
    :func:`trio.current_time`,
    :func:`trio.lowlevel.spawn_system_task`,
    :func:`trio.lowlevel.current_trio_token`, etc.
  * When a starting function raises before calling
    :func:`trio.TaskStatus.started`,
    :func:`trio.Nursery.start` will no longer wrap the exception
    in an undocumented :exc:`ExceptionGroup`.
  * To better reflect the underlying thread handling semantics,
    the keyword argument for `trio.to_thread.run_sync` that was

• Files Changed
• Browse Source

- Update to 0.22.2:
  * Fix PermissionError when importing trio due to trying to
    access pthread.
  * Breaking change: Timeout functions now raise ValueError if
    passed math.nan. This includes trio.sleep, trio.sleep_until,
    trio.move_on_at, trio.move_on_after, trio.fail_at and
    trio.fail_after.
  * Added support for naming threads created with
    trio.to_thread.run_sync, requires pthreads so is only
    available on POSIX platforms with glibc installed.
  * trio.socket.socket now prints the address it tried to connect
    to upon failure.
  * Fixed a crash that can occur when running Trio within an
    embedded Python interpreter, by handling the TypeError that
    is raised when trying to (re-)install a C signal handler.
  * Fix sniffio.current_async_library() when Trio tasks are
    spawned from a non-Trio context (such as when using
    trio-asyncio). Previously, a regular Trio task would inherit
    the non-Trio library name, and spawning a system task would
    cause the non-Trio caller to start thinking it was Trio.
  * Documented that Nursery.start_soon does not guarantee task
    ordering.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- remove buildrequires that are not used on sle15
  * If you want to use Trio, but are stuck with some other event loop
    memory channels slightly smaller and faster.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

SR for python stack proposal

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Try again with 0.22.0 and a fixed httpcore

- go back to 0.21.0 as it breaks httpcore

• Files Changed
• Browse Source