Skip to content
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

[WIP][ENG-5213] - Updated usage of osf:develop and Python 3.10 support #10540

Merged
merged 5 commits into from
Feb 20, 2024
Merged

[WIP][ENG-5213] - Updated usage of osf:develop and Python 3.10 support #10540

merged 5 commits into from
Feb 20, 2024

Conversation

ly-mariia
Copy link
Contributor

Purpose

Phase 1

Changes

  • Updated usage of osf:develop image in docker-compose.yml
  • Updated requirements.txt to support Python 3.10

QA Notes

Please make verification statements inspired by your code and what your code touches.

  • Verify
  • Verify

What are the areas of risk?

Any concerns/considerations/questions that development raised?

Documentation

Side Effects

Ticket

https://openscience.atlassian.net/browse/ENG-5213

Copy link
Member

@felliott felliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, @ly-mariia! I just thought of something that was mentioned in the original ticket. Since we would like to do another dep upgrade for python 3.11 soon, it would be nice if we could go back to our old deps with out having to rebuild requirements entirely. Could you rename the requirements volume to have 3.10 somewhere in the name? Something like osf_requirements_3_10_vol. If we start working on the 3.11 upgrade and have to switch back b/c QA finds a bug in the 3.10 code, we can just s/osf_requirements_3_11_vol/osf_requirements_3_10_vol/ instead of rebuilding.

@ly-mariia ly-mariia changed the title [ENG-5213] - Updated usage of osf:develop and Python 3.10 support [WIP][ENG-5213] - Updated usage of osf:develop and Python 3.10 support Feb 9, 2024
ly-mariia and others added 5 commits February 15, 2024 21:19
- Updated requirements.txt to support Python 3.10
 * The elasticsearch deps are tied to the version of the es service
   being run. Revert back to the previous dep until we can upgrade es.

 * Make a new volume for 3.10 deps. While working on this project,
   this will make switching back to the old 3.6 based version easier
   (just swap which volumes are commented).
@felliott felliott merged commit d467dbe into CenterForOpenScience:feature/python-upgrade Feb 20, 2024
1 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants