chore: update requirements for maple version #215
Merged
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.
Description
This PR updates the dependencies basically by adding in the base.in:
And organized the constraints in base, test and peer dependency.
To avoid problems with updating packages, some constraints were also added.
Note: to run this I did it with the platform version of pip-tools==6.4.0 and pip < 22 (Issue with pip, pip>22 support is given in another release(6.6.0)).
Testing instructions
When installing the plugin on a platform Maple has
openedx-events
in the version of the platform.Other information
The criterion I used to know whether to add the constraint or not was that when doing the make upgrade the requirement changed more than the patch version. If the package updated minor or major, I restricted it to what directly comes out on the platform (this with the justification that some packages do not version well and breaking changes are made in minor); this way we make sure that the requirements are as in the platform.
This time I had to restrict a lot because maple was out a long time ago and the packages have been updated, but I would expect this not to happen often.
Checklist for Merge