I would expect them only to be test dependencies for the project itself, not pulled in for downstream projects that use pprp.
I think the change came as part of 90b3d0c7bcc4f10f2349432a3131940d64f545d5, but I'm not very familiar with setup.py and packaging python libraries, so can't easily offer a code change to fix it.
If I upgrade using poetry with
poetry update --lock pprp
, I getnose
andcoverage
installed as non-dev dependencies.In a vanilla Python 3.7 virtualenv:
Is that expected behaviour?
I would expect them only to be test dependencies for the project itself, not pulled in for downstream projects that use pprp.
I think the change came as part of 90b3d0c7bcc4f10f2349432a3131940d64f545d5, but I'm not very familiar with setup.py and packaging python libraries, so can't easily offer a code change to fix it.