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
The requirements in the documentation do not seem to be complete. Ideally, it would be even better to specify versions of the libraries used because there is no guarantee that any future version of a dependency would not break the whole project. I feel like defining these dependencies further with versions in the documentation and in the requirements.txt is better way to go. I have found the set of requiremnts that seem to be working well on Linux and I can make a PR with them.
The text was updated successfully, but these errors were encountered:
Why do you ask, instead of just creating the PR to let others have a look at your proposal? Locking versions to a specific one will block any security fixes in dependencies to flow automatically into new installations, so there is a downside to fixed versions in requirements too. No idea which feature is most important here, though.
The requirements in the documentation do not seem to be complete. Ideally, it would be even better to specify versions of the libraries used because there is no guarantee that any future version of a dependency would not break the whole project. I feel like defining these dependencies further with versions in the documentation and in the
requirements.txt
is better way to go. I have found the set of requiremnts that seem to be working well on Linux and I can make a PR with them.The text was updated successfully, but these errors were encountered: