-
Notifications
You must be signed in to change notification settings - Fork 10
feat(setup): Update pythong version to 3.12 for RDM #545
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,6 +18,7 @@ install_requires = | |
| sentry-sdk>=1.45,<2.0.0 | ||
| cds-dojson @ git+https://github.com/CERNDocumentServer/cds-dojson@master#egg=cds-dojson | ||
| invenio-rdm-migrator>=5.0.0 | ||
| setuptools<82.0.0 # `invenio-rdm-migrator` has a dependency on `pypeln` which depends on `pkg_resources` | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what about the invenio-query-parser dependency we discussed?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is pypeln needed in invenio-migrator? can we eliminate it? otherwise we are not upgrading for performance if we depend on older setuptools and calling pkg_resources somewhere in the code
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Invenio-query-parser problem is described above in the setup.cfg file As for pypeln yes it's being used: https://github.com/search?q=repo%3Ainveniosoftware%2Finvenio-rdm-migrator%20pypeln&type=code
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is it used for anything? If not then we can remove without involving Alex
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes It is used for multi processing, in the transform run step and either we need to find an alternative for it or pin setuptools
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can you finalise the upgrade without pinning setuptools? |
||
| lxml>=4.6.5 | ||
| ipython!=8.1.0 | ||
| uwsgi>=2.0 | ||
|
|
||
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.
will this work in production image? for some time we will need backwards compatibility with 3.9 until we update invenio image to run newer versions
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.
No it is a breaking change, in python3.10
for backwards compatibility, i can add a try catch
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.
please make it work in both 3.9 and higher version because we are not yet ready to switch the prod image