You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pytest-cases depends on decopatch and makefun. decopatch and makefun depends on pytest-cases. This is problematic for distributions as constellationa like that require additional work or don't allow to run the test suite.
makefun does not require any of the other two at runtime (see installation requirements here)
Not for runtime but for the tests as mentioned in the first comment (I updated the title to reflect that). pytest-cases is a test requirement for makefun.
It's works for PyPI and other distribution channels as they don't require to run the tests. For most operating system distributions is preferred to run the test suite when ever possible during the build process for the packages to rise the quality.
I know that distro packaging is no the primary concern of developers 😉
See smarie/python-decopatch#20 (comment) that might be related. It is basically a matter of what you choose to package in RPMs: applications (including all the libraries they require) or individual libraries. If you choose to package individual python libraries, then the best quality you can aim for is the one of PyPi and conda, the reference repositories.
That being said, for the present situation, I would recommend to separate
the test dependencies (where you do not need to ensure compat with the versions installed in the distro)
from the runtime dependencies, where indeed it is good that you check compliance with the distribution at hand
To reach this objective you could run the tests in a venv/virtualenv. That way the test dependencies can be anything (any version).
Hi @fabaff coming back to you about this issue: how does it sound to run the tests of each package in a venv/virtualenv ? Would it solve your circular deps issue for packaging ? Let me know.
Note that for most of my projects I try to migrate to using github actions and nox, so it is relatively easy to run the tests: simply running nox does the trick.
Activity
smarie commentedon May 4, 2021
Thanks @fabaff for your feedback.
makefundoes not require any of the other two at runtime (see installation requirements here)decopatchsolely requiresmakefunat runtime (see installation requirements here)And finally
pytest-casesrequires both (see here).So there is no circular dependency, and this is why the three packages can be released on PyPi and Conda forge without issues.
What do you try to achieve and why ?
[-]Remove circular dependency[/-][+]Remove circular dependency for tests[/+]fabaff commentedon May 5, 2021
Not for runtime but for the tests as mentioned in the first comment (I updated the title to reflect that).
pytest-casesis a test requirement formakefun.It's works for PyPI and other distribution channels as they don't require to run the tests. For most operating system distributions is preferred to run the test suite when ever possible during the build process for the packages to rise the quality.
I know that distro packaging is no the primary concern of developers 😉
smarie commentedon May 5, 2021
See smarie/python-decopatch#20 (comment) that might be related. It is basically a matter of what you choose to package in RPMs: applications (including all the libraries they require) or individual libraries. If you choose to package individual python libraries, then the best quality you can aim for is the one of PyPi and conda, the reference repositories.
That being said, for the present situation, I would recommend to separate
To reach this objective you could run the tests in a
venv/virtualenv. That way the test dependencies can be anything (any version).smarie commentedon Jun 1, 2021
Hi @fabaff coming back to you about this issue: how does it sound to run the tests of each package in a venv/virtualenv ? Would it solve your circular deps issue for packaging ? Let me know.
Note that for most of my projects I try to migrate to using github actions and nox, so it is relatively easy to run the tests: simply running nox does the trick.