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

126 provide some backwards compatibility with previous python versions #127

Conversation

asgibson
Copy link
Contributor

CI runs show unit test compatibility with Python versions 3.8 thru 3.12.
While this does not ensure "production" usage of OnAIR it does show that all the code used is compatible with those versions.
Python 3.7 was found to have many issues with running unit tests.
It is recommended to stop at 3.8 for now because allowing for Python 3.7 would require more time and effort.

@asgibson asgibson added enhancement New feature or request convention Repository coding and documentation standards labels Mar 15, 2024
@asgibson asgibson self-assigned this Mar 15, 2024
@asgibson asgibson linked an issue Mar 15, 2024 that may be closed by this pull request
@asgibson asgibson force-pushed the 126-provide-some-backwards-compatibility-with-previous-python-versions branch 3 times, most recently from faeed87 to 897f0fb Compare March 26, 2024 16:40
Updated dependencies to allow for 3.9-3.11
Updated dependencies to not require specific versions of other packages
Updated unit-test.yml to run under 3.9, 3.10 and 3.11
For unknown reason using 3.9, 3.10, and 3.11 used 3.9, 3.1, and 3.11
  3.1 failed because environment.yml only allowed 3.9-3.11
Retrying with just 3.11 to ensure previously working version works with matrix
GitHub warning prompted this change:
  Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20:
  actions/checkout@v3, codecov/codecov-action@v3.
  Node.js 16 actions are deprecated. For more information see:
  https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
See if it is still operational with checkout at v4
Previous CI failed correctly, 3.8 not allowed in env
@asgibson asgibson force-pushed the 126-provide-some-backwards-compatibility-with-previous-python-versions branch from 897f0fb to 086ca73 Compare April 8, 2024 19:28
Copy link
Contributor

@the-other-james the-other-james 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. I tested on my own docker setup.

@asgibson asgibson merged commit 3d37964 into main Apr 9, 2024
10 checks passed
@asgibson asgibson deleted the 126-provide-some-backwards-compatibility-with-previous-python-versions branch April 9, 2024 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
convention Repository coding and documentation standards enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide some backwards compatibility with previous Python versions
2 participants