-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
PEP 582: Possible new API in sysconfig for paths/scheme #3013
Comments
Should this be an issue on the PEPs repo, or would it be more appropriate as a CPython issue and/or Packaging Discourse discussion? At least historically, issues in the PEPs repo have mostly been used for meta items related to the PEPs process, infra, theme, etc. itself, and to document and discuss editorial defects in existing PEPs, whereas discussion of substantive changes to CPython or PEP content are directed elsewhere. |
It could maybe be in then steering council repo also? |
I'd suggest that this be on Kushal's fork's issue tracker instead. |
I'm not sure the SC repo is the place to brainstorm new potential additions to a particular PEP— I would suggest only bringing it to the SC's attention if nessesary when submitting the PEP for final approval. As Pradyun suggested, Kushal's fork would be a great place for that. |
Closing this issue as I opened kushaldas#3 |
Right now PEP 582 asks for a new
scheme
in thesysconfig
module. But, a possible another option is a new API (function) and then the tools will have to build up the whole scheme using it.Having a full scheme helps, but this is the option was suggested by @FFY00.
The text was updated successfully, but these errors were encountered: