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
currently, we have a list of required python packages in the setup.py (versions not fixed), and a set of fixed versions in requirements.txt and requirements-optional.txt.
One common issue is that even for fixed packages versions, the versions of dependencies of these packages can still change - this issue is addressed by pipenv.
It turns out we already have a Pipfile in the repository but it isn't mentioned anywhere.
The text was updated successfully, but these errors were encountered:
Closing this issue, as I believe we in other issues have decided to use the current setup, i.e., have ~= specified dependencies in setup.py and then check the dependencies with GitHub Actions CI through special requirements.txt used only for these tests.
currently, we have a list of required python packages in the setup.py (versions not fixed), and a set of fixed versions in requirements.txt and requirements-optional.txt.
One common issue is that even for fixed packages versions, the versions of dependencies of these packages can still change - this issue is addressed by pipenv.
It turns out we already have a
Pipfile
in the repository but it isn't mentioned anywhere.The text was updated successfully, but these errors were encountered: