-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bump python 3.12 and maintenance updates #258
Conversation
Why these changes are being introduced: Some new CLI application project structures, linting, and testing conventions were established in 2023. This is the first time this project has receieved maintenance updates since that time. Additionally, this commit bumps the python version to 3.12. How this addresses that need: * Bumps python version in required areas * Establishes new linting and testing conventions * Updates files to meet new linting requirements Side effects of this change: * None Relevant ticket(s): * None
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.
Looks great! Some minor suggestions
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.
Just a few minor comments but looking good!
FYI @ehanson8 , @jonavellecuerdo - new commits based on code review suggestions. |
Tested with sample data in stage environment. LGTM. |
What does this PR do?
Bumps python version to 3.12, and updates structure of project linting and testing to new conventions.
Most changes were syntactical to meet new linting requirements, but a couple of repeated changes are somewhat meaningful:
datetime
objects are now UTC timezone awaredatetime.datetime(...)
was used, now includestzinfo=datetime.UTC
datetime.strptime(...)
is used,.replace(tzinfo=datetime.UTC)
is included to replace the timezone with UTC, but keep the original 00:00 hours/minutes when parsing theYYYY-MM-DD
date string without hours or minutes presenttzinfo=...
was used, this would bump the hours +4 hours to UTC time upon parsing, which while likely inconsequential, is not ideal, given theYYYY-MM-DD
timestamp has no notion of hours or minutesNOTE: Testing has not yet been confirmed in Dev1 or Stage. This will happen with help from @adamshire123 before a release is tagged.
Helpful background context
This project was using python 3.11 before this PR, and had not receieved any maintenance updates to match new patterns for linting and testing established recently.
How can a reviewer manually see the effects of these changes?
Tests run, linting passes.
As mentioned above, manual integration tests that require access to Terraform and Alma console will be performed with help from @adamshire123 (or someone else with access).
Includes new or updated dependencies?
YES
What are the relevant tickets?
None
Developer
Code Reviewer
(not just this pull request message)