-
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
Change Readme to clearly point out that the project is not worked on any more. #163
Comments
|
@misuzu that is a very helpful hint. |
justpy-org/justpy@2db41e0 shows the kind of necessary refactoring |
bhearsum
added a commit
to bhearsum/balrog
that referenced
this issue
Jan 24, 2023
This project or more or less dead (see Martiusweb/asynctest#163), and will prevent us from updating to a more modern Python.
bhearsum
added a commit
to bhearsum/balrog
that referenced
this issue
Jan 24, 2023
This project or more or less dead (see Martiusweb/asynctest#163), and will prevent us from updating to a more modern Python.
bhearsum
added a commit
to mozilla-releng/balrog
that referenced
this issue
Jan 24, 2023
* Fix caching in balrogagent tests * Get rid of asynctest usage This project or more or less dead (see Martiusweb/asynctest#163), and will prevent us from updating to a more modern Python.
This was referenced Feb 13, 2023
This was referenced Mar 13, 2023
This was referenced Mar 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#161 starts being a showstopper for python 3.11 and if no new maintainers step in this project is not useable any more soon.
#158 already asked the question and @Martiusweb Martin Richard's answer was straightforward I'll not work on asynctest anymore, and I believe unittest.mock.AsyncMock in combination with pytest is probably your best bet for now.
IMHO this should be stated as one of the first sentences in the README
The text was updated successfully, but these errors were encountered: