1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
Release history
===============
.. currentmodule:: outcome
.. towncrier release notes start
Outcome 1.2.0 (2022-06-14)
--------------------------
Features
~~~~~~~~
- Add support for Python 3.9 and 3.10. (`#32 <https://github.com/python-trio/outcome/pull/32>`__)
Deprecations and Removals
~~~~~~~~~~~~~~~~~~~~~~~~~
- Drop support for Python 3.6. (`#32 <https://github.com/python-trio/outcome/pull/32>`__)
Outcome 1.1.0 (2020-11-16)
--------------------------
Bugfixes
~~~~~~~~
- Tweaked the implementation of ``Error.unwrap`` to avoid creating a
reference cycle between the exception object and the ``unwrap``
method's frame. This shouldn't affect most users, but it slightly
reduces the amount of work that CPython's cycle collector has to do,
and may reduce GC pauses in some cases. (`#29 <https://github.com/python-trio/outcome/issues/29>`__)
Deprecations and Removals
~~~~~~~~~~~~~~~~~~~~~~~~~
- Drop support for Python 2.7, 3.4, and 3.5. (`#27 <https://github.com/python-trio/outcome/issues/27>`__)
Outcome 1.0.1 (2019-10-16)
--------------------------
Upgrade to attrs 19.2.0.
Outcome 1.0.0 (2018-09-12)
--------------------------
Features
~~~~~~~~
- On Python 3, the exception frame generated within :func:`capture` and
:func:`acapture` has been removed from the traceback.
(`#21 <https://github.com/python-trio/outcome/issues/21>`__)
- Outcome is now tested using asyncio instead of trio, which outcome is a
dependency of. This makes it easier for third parties to package up Outcome.
(`#13 <https://github.com/python-trio/outcome/issues/13>`__)
Outcome 0.1.0 (2018-07-10)
--------------------------
Features
~~~~~~~~
- An Outcome may only be unwrapped or sent once.
Attempting to do so a second time will raise an :class:`AlreadyUsedError`.
(`#7 <https://github.com/python-trio/outcome/issues/7>`__)
|
