-
Notifications
You must be signed in to change notification settings - Fork 30
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
Inquiry about the status of pytest-lazy-fixture and offering assistance #63
Comments
You may also consider transferring the plugin to the pytest-dev organization as described here: https://github.com/pytest-dev/pytest/blob/main/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev |
No, as I didn't find their email |
You can find his email address in the metadata of the last commits in the main branch. github won't show the information for privacy issues I guess, but just |
There is already this issue, I don't think sending an email would make a difference. |
It's worth a try! Sometimes people have repo notifications turned off, and sometimes they use different emails for different things. |
I just sent an email |
Hey @TvoroG,
I hope you're doing well. I really find pytest-lazy-fixture a great pytest plugin, but I noticed that it hasn't had a release since 2020, and there are some open issues and pull requests that seem to be unattended.
For this reason, I wonder if the project is abandoned, or if it's still supported.
Specifically, I think that #62 is really something worth considering and that would make the project even more useful. I use that approach in pytest-factoryboy, but this project is way more advanced in the way it handles the pytest internals for lazy fixtures.
As an active user and maintainer of pytest-bdd and pytest-factoryboy, I would be interested in contributing to the project's maintenance and further development, including reviewing PRs, keeping the CI up to date with the latest pytests and python versions, making releases, etc.
Would that be something you can consider?
Thanks for your time, and I'm looking forward to your response.
Best regards,
Alessio
The text was updated successfully, but these errors were encountered: