-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fix #261 - pkg_resources migration #262
Conversation
Ok, tests pass at least, so time for some feedback! 😁 |
OMG! |
I think that since we are touching the code we should aim to support python >=3.9 only. Doesn't have to be in this PR, but we should update python both in the Dockerfile and in the actions. Is it a lot of refactoring in the code that you are introducing in this PR when we update python? |
We do have an image ready with python 3.11 and miniconda. I could work on one with python 3.12 and miniconda? |
Sounds great! I can switch to the 3.11+miniconda here directly. It would ofcourse be possible to build (or brew) outside of conda, but that would be a drop in replacement! |
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.
It looks good to me. Great refactoring! 💯
import pkg_resources | ||
try: | ||
from importlib.metadata import entry_points | ||
except ImportError: # Backport support for importlib metadata on Python 3.7 |
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.
Now I understand, it's for the Dockerfile!
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.
It doesn't hurt much, other than perhaps that we install the compat libs without using them, so I guess we just keep it.
@@ -16,14 +19,20 @@ | |||
|
|||
LOG = logging.getLogger(__name__) | |||
|
|||
COMMAND_GROUP_KEY = 'chanjo.subcommands.4' |
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.
What is this subcommands.4 group? I'm not familiar with this syntax
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.
As far as I understood it's just a label (
Line 96 in 1b2d859
'chanjo.subcommands.4': [ |
Co-authored-by: Chiara Rasi <rasi.chiara@gmail.com>
Deployed to stage:
Testing a case:
|
Description
Fixed
I have aimed to have it safe for python >=3.9. As the PR is now, it might theoretically work back to 3.5/3.7 something, but also definitely with 3.13. More input on what we should support welcome. If we leave 3.7, we must update the
Dockerfile
as well, which currently runs an old 3.7 alpine. 🙄How to prepare for test
us
paxa
How to test
Expected test outcome
Review
Thanks for filling in who performed the code review and the test!
This version is a
Implementation Plan