Hi !
I'm working on a new package proposal for django-health-check [1] and one of it's test requirements is pytest-django. I naively attempted to use the python3-django-pytest [2] package in BuildRequires and soon noticed that the tests in %check would not pass.
A bit of research later, I found out that there are projects named django-pytest [3] and pytest-django [4] on pypi. Great. The former is based on an upstream that hasn't been updated since 2012 [5] while the latter has been actively maintained [6].
Unless mistaken, we do not currently have a package for the maintained version, pytest-django. I guess the right thing to do would be to create a new package for pytest-django ?
I don't have the bandwidth to take care of pytest-django right now. Would it be acceptable to propose a new package without %check until it gets packaged ?
Thanks !
[1]: https://github.com/KristianOellegaard/django-health-check [2]: https://koji.fedoraproject.org/koji/packageinfo?packageID=13680 [3]: https://pypi.org/project/django-pytest [4]: https://pypi.org/project/pytest-django [5]: https://github.com/dusty-phillips/django-pytest [6]: https://github.com/pytest-dev/pytest-django
"DM" == David Moreau-Simard dmsimard@redhat.com writes:
DM> I don't have the bandwidth to take care of pytest-django right now. DM> Would it be acceptable to propose a new package without %check until DM> it gets packaged ?
It's OK to disable tests you can't run because they have additional dependencies which aren't in the distribution, though certainly the alternative of packaging that dependency and running all of the tests is preferable.
- J<
python-devel@lists.fedoraproject.org