| 1 |
Release history |
| 2 |
=============== |
| 3 |
|
| 4 |
.. currentmodule:: pytest_trio |
| 5 |
|
| 6 |
.. towncrier release notes start |
| 7 |
|
| 8 |
pytest-trio 0.8.0 (2022-11-01) |
| 9 |
------------------------------ |
| 10 |
|
| 11 |
Features |
| 12 |
~~~~~~~~ |
| 13 |
|
| 14 |
- If a test raises an ``ExceptionGroup`` (or nested ``ExceptionGroup``\ s) with only |
| 15 |
a single 'leaf' exception from ``pytest.xfail()`` or ``pytest.skip()``\ , we now |
| 16 |
unwrap it to have the desired effect on Pytest. ``ExceptionGroup``\ s with two or |
| 17 |
more leaf exceptions, even of the same type, are not changed and will be treated |
| 18 |
as ordinary test failures. |
| 19 |
|
| 20 |
See `pytest-dev/pytest#9680 <https://github.com/pytest-dev/pytest/issues/9680>`__ |
| 21 |
for design discussion. This feature is particularly useful if you've enabled |
| 22 |
`the new strict_exception_groups=True option |
| 23 |
<https://trio.readthedocs.io/en/stable/reference-core.html#strict-versus-loose-exceptiongroup-semantics>`__. (`#104 <https://github.com/python-trio/pytest-trio/issues/104>`__) |
| 24 |
|
| 25 |
|
| 26 |
Bugfixes |
| 27 |
~~~~~~~~ |
| 28 |
|
| 29 |
- Fix an issue where if two fixtures are being set up concurrently, and |
| 30 |
one crashes and the other hangs, then the test as a whole would hang, |
| 31 |
rather than being cancelled and unwound after the crash. (`#120 <https://github.com/python-trio/pytest-trio/issues/120>`__) |
| 32 |
|
| 33 |
|
| 34 |
Misc |
| 35 |
~~~~ |
| 36 |
|
| 37 |
- Trio 0.22.0 deprecated ``MultiError`` in favor of the standard-library |
| 38 |
(or `backported <https://pypi.org/project/exceptiongroup/>`__) ``ExceptionGroup`` |
| 39 |
type; ``pytest-trio`` now uses ``ExceptionGroup`` exclusively and therefore requires |
| 40 |
Trio 0.22.0 or later. (`#128 <https://github.com/python-trio/pytest-trio/issues/128>`__) |
| 41 |
|
| 42 |
- Dropped support for end-of-life Python 3.6, and the ``async_generator`` library |
| 43 |
necessary to support it, and started testing on Python 3.10 and 3.11. (`#129 <https://github.com/python-trio/pytest-trio/issues/129>`__) |
| 44 |
|
| 45 |
|
| 46 |
pytest-trio 0.7.0 (2020-10-15) |
| 47 |
------------------------------ |
| 48 |
|
| 49 |
Features |
| 50 |
~~~~~~~~ |
| 51 |
|
| 52 |
- Support added for :ref:`alternative Trio run functions <trio-run-config>` via the ``trio_run`` configuration variable and ``@pytest.mark.trio(run=...)``. Presently supports Trio and QTrio. (`#105 <https://github.com/python-trio/pytest-trio/issues/105>`__) |
| 53 |
|
| 54 |
|
| 55 |
Deprecations and Removals |
| 56 |
~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 57 |
|
| 58 |
- Python 3.5 support removed. (`#96 <https://github.com/python-trio/pytest-trio/issues/96>`__) |
| 59 |
|
| 60 |
|
| 61 |
pytest-trio 0.6.0 (2020-05-20) |
| 62 |
---------------------------------- |
| 63 |
|
| 64 |
Features |
| 65 |
~~~~~~~~ |
| 66 |
|
| 67 |
- Incompatible change: if you use ``yield`` inside a Trio fixture, and |
| 68 |
the ``yield`` gets cancelled (for example, due to a background task |
| 69 |
crashing), then the ``yield`` will now raise :exc:`trio.Cancelled`. |
| 70 |
See :ref:`cancel-yield` for details. Also, in this same case, |
| 71 |
pytest-trio will now reliably mark the test as failed, even if the |
| 72 |
fixture doesn't go on to raise an exception. (`#75 <https://github.com/python-trio/pytest-trio/issues/75>`__) |
| 73 |
|
| 74 |
- Updated for compatibility with Trio v0.15.0. |
| 75 |
|
| 76 |
|
| 77 |
pytest-trio 0.5.2 (2019-02-13) |
| 78 |
------------------------------ |
| 79 |
|
| 80 |
Features |
| 81 |
~~~~~~~~ |
| 82 |
|
| 83 |
- pytest-trio now makes the Trio scheduler deterministic while running |
| 84 |
inside a Hypothesis test. Hopefully you won't see any change, but if |
| 85 |
you had scheduler-dependent bugs Hypothesis will be more effective now. (`#73 <https://github.com/python-trio/pytest-trio/issues/73>`__) |
| 86 |
|
| 87 |
- Updated for compatibility with trio v0.11.0. |
| 88 |
|
| 89 |
pytest-trio 0.5.1 (2018-09-28) |
| 90 |
------------------------------ |
| 91 |
|
| 92 |
Bugfixes |
| 93 |
~~~~~~~~ |
| 94 |
|
| 95 |
- The pytest 3.8.1 release broke pytest-trio's handling of trio tests |
| 96 |
defined as class methods. We fixed it again. (`#64 <https://github.com/python-trio/pytest-trio/issues/64>`__) |
| 97 |
|
| 98 |
|
| 99 |
pytest-trio 0.5.0 (2018-08-26) |
| 100 |
------------------------------ |
| 101 |
|
| 102 |
This is a major release, including a rewrite of large portions of the |
| 103 |
internals. We believe it should be backwards compatible with existing |
| 104 |
projects. Major new features include: |
| 105 |
|
| 106 |
* "trio mode": no more writing ``@pytest.mark.trio`` everywhere! |
| 107 |
* it's now safe to use nurseries inside fixtures (`#55 |
| 108 |
<https://github.com/python-trio/pytest-trio/issues/55>`__) |
| 109 |
* new ``@trio_fixture`` decorator to explicitly mark a fixture as a |
| 110 |
trio fixture |
| 111 |
* a number of easy-to-make mistakes are now caught and raise |
| 112 |
informative errors |
| 113 |
* the :data:`nursery` fixture is now 87% more magical |
| 114 |
|
| 115 |
For more details, see the manual. Oh right, speaking of which: we |
| 116 |
finally have a manual! You should read it. |
| 117 |
|
| 118 |
|
| 119 |
pytest-trio 0.4.2 (2018-06-29) |
| 120 |
------------------------------ |
| 121 |
|
| 122 |
Features |
| 123 |
~~~~~~~~ |
| 124 |
|
| 125 |
- pytest-trio now integrates with `Hypothesis |
| 126 |
<https://hypothesis.readthedocs.io>`_ to support ``@given`` on async tests |
| 127 |
using Trio. (`#42 <https://github.com/python-trio/pytest-trio/issues/42>`__) |
| 128 |
|
| 129 |
|
| 130 |
pytest-trio 0.4.1 (2018-04-14) |
| 131 |
------------------------------ |
| 132 |
|
| 133 |
No significant changes. |
| 134 |
|
| 135 |
|
| 136 |
pytest-trio 0.4.0 (2018-04-14) |
| 137 |
------------------------------ |
| 138 |
|
| 139 |
- Fix compatibility with trio 0.4.0 (`#25 |
| 140 |
<https://github.com/python-trio/pytest-trio/pull/36>`__) |
| 141 |
|
| 142 |
|
| 143 |
pytest-trio 0.3.0 (2018-01-03) |
| 144 |
------------------------------ |
| 145 |
|
| 146 |
Features |
| 147 |
~~~~~~~~ |
| 148 |
|
| 149 |
- Add ``nursery`` fixture and improve teardown handling for yield fixture (`#25 |
| 150 |
<https://github.com/python-trio/pytest-trio/issues/25>`__) |
| 151 |
|
| 152 |
|
| 153 |
pytest-trio 0.2.0 (2017-12-15) |
| 154 |
------------------------------ |
| 155 |
|
| 156 |
- Heavy improvements, add async yield fixture, fix bugs, add tests etc. (`#17 |
| 157 |
<https://github.com/python-trio/pytest-trio/issues/17>`__) |
| 158 |
|
| 159 |
|
| 160 |
Deprecations and Removals |
| 161 |
~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 162 |
|
| 163 |
- Remove unused_tcp_port{,_factory} fixtures (`#15 |
| 164 |
<https://github.com/python-trio/pytest-trio/issues/15>`__) |
| 165 |
|
| 166 |
|
| 167 |
pytest-trio 0.1.1 (2017-12-08) |
| 168 |
------------------------------ |
| 169 |
|
| 170 |
Disable intersphinx for trio (cause crash in CI for the moment due to 404 |
| 171 |
in readthedoc). |
| 172 |
|
| 173 |
|
| 174 |
pytest-trio 0.1.0 (2017-12-08) |
| 175 |
------------------------------ |
| 176 |
|
| 177 |
Initial release. |