-
Notifications
You must be signed in to change notification settings - Fork 69
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
feat: --about to list the python versions supported by the connector #1628
Comments
If you don't need the parsed version range, then this a relatively low effort as we're already using Also, fwiw in the script where you install the package to run |
This is related to: We'll need to align the Hub with the SDK on this but I'm very supportive of making this happen! |
Getting the @edgarrmondragon @pnadolny13 In light of the above, here are two approaches we should consider:
|
@WillDaSilva I vote for 2. It's probably better to return the raw specifier and let downstream consumers get the details they need by parsing it. |
@edgarrmondragon Agreed that that info should be provided. Thoughts on doing both? Providing the raw specifier, and also parsing some more immediately useful info out of it. |
@WillDaSilva Yeah, that makes sense. Your example is a good start. |
It would be great if SDK plugins would advertise their supported python versions. This way we can scrape them for:
I'm not exactly sure what format this should be in but something like whats in the pypoetry.toml would probably work
python = "<3.12,>=3.7.1"
cc @WillDaSilva
The text was updated successfully, but these errors were encountered: