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
At the moment a broken pyup badge is in the README.rst, which is a not too pretty artifact from the coociecutter template. The solution for this would to eigther drop the badge or start using pyup.
Pros and Cons on using pyup: Pros:
pyup makes automated PRs when new versions of dependencies are released (automated testing due to the CIs, which garantees functionality new versions of dependencies)
Cons:
can be "spammy" if many updates of dependencies are released
will lead to merge conficts, with its own PRs, if ignored too long
PS.: Pyup only triggers on fixed versions (i.e.: pytest==3.0.5) not on minimum requirements (i.e.: pytest>=3.0.5), so by convention this should only affect requirements_dev.txt since it is bad practice to fix versions in the setup.py
The text was updated successfully, but these errors were encountered:
At the moment a broken pyup badge is in the
README.rst
, which is a not too pretty artifact from the coociecutter template. The solution for this would to eigther drop the badge or start using pyup.Pros and Cons on using pyup:
Pros:
Cons:
PS.: Pyup only triggers on fixed versions (i.e.:
pytest==3.0.5
) not on minimum requirements (i.e.:pytest>=3.0.5
), so by convention this should only affectrequirements_dev.txt
since it is bad practice to fix versions in thesetup.py
The text was updated successfully, but these errors were encountered: