-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update requirements #24
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,42 +1,36 @@ | ||
# | ||
# This file is autogenerated by pip-compile with Python 3.8 | ||
# This file is autogenerated by pip-compile with Python 3.11 | ||
# by the following command: | ||
# | ||
# make upgrade | ||
# | ||
blinker==1.7.0 | ||
blinker==1.8.2 | ||
# via flask | ||
certifi==2024.2.2 | ||
certifi==2024.8.30 | ||
# via requests | ||
charset-normalizer==3.3.2 | ||
charset-normalizer==3.4.0 | ||
# via requests | ||
click==8.1.7 | ||
# via flask | ||
edx-codejail==3.2.0 | ||
# via | ||
# -c requirements/constraints.txt | ||
# -r requirements/base.in | ||
edx-codejail==3.5.1 | ||
# via -r requirements/base.in | ||
flask==3.0.3 | ||
# via -r requirements/base.in | ||
idna==3.7 | ||
idna==3.10 | ||
# via requests | ||
importlib-metadata==7.1.0 | ||
# via flask | ||
itsdangerous==2.2.0 | ||
# via flask | ||
jinja2==3.1.3 | ||
jinja2==3.1.4 | ||
# via flask | ||
markupsafe==2.1.5 | ||
markupsafe==3.0.2 | ||
# via | ||
# jinja2 | ||
# werkzeug | ||
requests==2.31.0 | ||
requests==2.32.3 | ||
# via -r requirements/base.in | ||
six==1.16.0 | ||
# via edx-codejail | ||
urllib3==2.2.1 | ||
urllib3==2.2.3 | ||
# via requests | ||
werkzeug==3.0.2 | ||
werkzeug==3.0.4 | ||
# via flask | ||
zipp==3.18.1 | ||
# via importlib-metadata |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,14 @@ | ||
# | ||
# This file is autogenerated by pip-compile with Python 3.8 | ||
# This file is autogenerated by pip-compile with Python 3.11 | ||
# by the following command: | ||
# | ||
# make upgrade | ||
# | ||
wheel==0.43.0 | ||
wheel==0.44.0 | ||
# via -r requirements/pip.in | ||
|
||
# The following packages are considered to be unsafe in a requirements file: | ||
pip==24.0 | ||
pip==24.2 | ||
# via -r requirements/pip.in | ||
setuptools==69.5.1 | ||
setuptools==75.2.0 | ||
# via -r requirements/pip.in |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're dropping the tests for Python 3.8, and we can no longer guarantee compatibility with Quince, should we bump the version, add an entry to the changelog, and update the compatibility table?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This plugin follows the tutor versioning convention, so this version (v17.x.x) doesn't necessarily support quince, although no significant changes have been made for a while. This makes me question if this plugin (edit: service) should follow the same convention that demands a new version each release cause we've been using the same for a while.
Now that Maga mentioned the compatibility table, can we update it to reflect the current plugin (edit: service) state?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reminder that this is not a Tutor plugin, this is essentially an IDA,
tutor-contrib-codejail
is the one that follows the Tutor versioning scheme. The actual plugin uses the compatible code of codejailservice for each release.We decided to change the versioning scheme in redwood (see: #22). What should happen is that a new sumac branch is created,
tutor-contrib-codejail
builds using that branch until the release is ready and after that we tagsumac.1
. I don't think the compatibility table in this repo is useful and I would rather remove it.One thing that can be improved though, we should tag the other point-releases when they are ready.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, sorry. I edited my comment so it references the service instead.
I wasn't aware of the change in the versioning scheme. Should we remove the service releases to make it less confusing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it makes sense, we can leave them up for history reasons, but it'd be good to drop the compatibility table that reference that release convention.