-
Notifications
You must be signed in to change notification settings - Fork 41
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 case failures in Python 3.8 #132
Comments
Any progress here? Fedora 32 is going to ship with Python 3.8 and it'd be great to have a package that passes all tests by Beta Freeze latest (late February 2020). |
Ping. Is this package alive? |
Since AsyncMock landed in Python 3.8, people should use AsyncMock and .
AsyncMock breaks asynctest in ways that make it hard to fix correctly, and
I have time/resources to spend on this package.
Maybe we can just remove code related to old-style coroutines and fix most
issues, but I can't promise when this will be done.
Le lun. 27 avr. 2020 à 08:34, Michał Górny <[email protected]> a
écrit :
… Ping. Is this package alive?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#132 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABPWGGCA33XODC2UVNHIBTROURPLANCNFSM4H4K2RIA>
.
--
Martin <http://www.martiusweb.net> Richard
www.martiusweb.net
|
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are some test failures in CPython master and also 3.8 beta 1. I guess the CI could be using an older version of 3.8. I tried some bisecting and on reverting changes made in https://bugs.python.org/issue36996 some cases are fixed. Recently unittest.mock.patch has support added for async functions to be mocked. I am not sure if asynctest tests needs to be changed or if there is a regression due to the linked CPython issue. I have filed DeprecationWarnings in Python 3.8 under #126 since it's of low priority. Test run log as below.
Thanks for asynctest that helped in AsyncMock design :)
The text was updated successfully, but these errors were encountered: