Relaxed constraints on dependency versions in requirements.txt #691
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The pinned version requirements are now more relaxed to prevent users from running into dependency conflicts when using FARM as one component within larger projects.
seqeval, dotmap
Removed the fixed version numbers. All tests passed with the different available versions of these libraries and I checked for a selection of the examples that they run as expected.
mlflow
Restricted the version to the latest available version 1.13.1 or lower. All tests passed and the logging works for the examples as expected for the different available versions of mlflow. The restriction ensures that any breaking changes in future versions of mlflow will not affect us.
Werkzeug
Kept the version as is because there are still compatibility issues with the more recent versions (>=1.0.0) as reported earlier: #250 Some smaller code changes would be needed if we decide to upgrade. For now, the best practice seems to be pinning the version number as is, e.g.: jarus/flask-testing#143
closes #669
closes #647