-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures with Python 3.10.0a7 #8546
Comments
As a fix, should I if-else the expected string on Python version? |
Thanks for the detailed report! Pretty strange that they just break Enum's
For this I think whichever way we fix it is fine - condition, make the
This is more tricky, because it may in turn break users who match on Enum-generated IDs. Probably not very common but still. The choices I see are (relevant code is here):
I think 3 is strictly better than 1, and 2 is better than 3. So my preference is 2. |
If all we need is a custom repr on the enum let's go for it |
Potential fix for pytest-dev#8546
I have a little bit newer Python 3.10.0a7 python/cpython@23acadc and the pytest does not work for me for a different reason:
I haven't had time to investigate more yet. It seems to be something very fresh in Python itself. I'll try to bisect the change today. |
@frenzymadness See #8539 and #8540. |
Fixed by #8540. |
Potential fix for pytest-dev#8546
- bump pytest to 6.2.4 (pytest-dev/pytest#8546) - pin tox-poetry-installer at 0.6.3 (enpaul/tox-poetry-installer#45)
We cannot run tests with Python 3.10 using Pytest 6.x due to [1]. This is fixed in Pytest 7.x but Pytest 7.x no longer supports Python 3.6 which aioresponses tries to support. However because Python 3.6 is already past the EOL date, the simplest solution is to no longer test with Python 3.6 and to stop declaring support for that version. [1] pytest-dev/pytest#8546
Our tests are filing on Python 3.10 due to [1] so we update Pytest in `requirements-dev.txt` to the latest version. [1] pytest-dev/pytest#8546
We cannot run tests with Python 3.10 using Pytest 6.x due to [1]. This is fixed in Pytest 7.x but Pytest 7.x no longer supports Python 3.6 which aioresponses tries to support. However because Python 3.6 is already past the EOL date, the simplest solution is to no longer test with Python 3.6 and to stop declaring support for that version. [1] pytest-dev/pytest#8546
Our tests are filing on Python 3.10 due to [1] so we update Pytest in `requirements-dev.txt` to the latest version. [1] pytest-dev/pytest#8546
We cannot run tests with Python 3.10 using Pytest 6.x due to [1]. This is fixed in Pytest 7.x but Pytest 7.x no longer supports Python 3.6 which aioresponses tries to support. However because Python 3.6 is already past the EOL date, the simplest solution is to no longer test with Python 3.6 and to stop declaring support for that version. [1] pytest-dev/pytest#8546
Our tests are filing on Python 3.10 due to [1] so we update Pytest in `requirements-dev.txt` to the latest version. [1] pytest-dev/pytest#8546
Hello, we see some test failures due to different reprs in Python 3.10.0a7.
This is on branch main, @ 9653a0e.
Fedora Linux 33, 34 or 35.
The first problem is here:
pytest/testing/test_pytester.py
Line 748 in 9653a0e
The second is here:
pytest/testing/python/metafunc.py
Line 451 in 9653a0e
This mgiht be related:
https://docs.python.org/3.10/whatsnew/3.10.html#enum says:
The text was updated successfully, but these errors were encountered: