Skip to content

Upgrade to using Python 3.10.4 #2421

@lisagoodrich

Description

@lisagoodrich

Describe the Task

Update any code necessary for upgrading to Python 3.10.4. We are taking this action because WCOSS2 is only allowing Python 3.10.4 to be used for operational installations. Therefore, we need to ensure that our next release uses Python 3.10.4.

Please also update .readthedocs.yaml with 3.10.4
Note that we decided NOT to upgrade to 3.10.4 since RTD supports up to 3.8.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.
(Assignee please fill this in once you know.)

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

Incorporate in a beta version as soon as possible to ensure there are no problems.

Funding Source

Please ask Tara before starting on this work.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Task Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Add any new Python packages to the METplus Components Python Requirements table.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions