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
Remove packaging from the stdlib #59352
Comments
Eric, this is for you. If you do only one thing before the 3.3 beta, please do this. |
Yep, that was on my planning for tonight or tomorrow afternoon. |
Very good, thanks. |
Just a note: a this time I am cleaning the apartment that I’m leaving, so when I say “Saturday afternoon” it’s in Montreal time, so you may see it as early Sunday from Europe. So don’t worry if your Saturday night comes and I did not commit. |
On it. |
The sysconfig module was modified (and sysconfig.cfg was introduced) to serve the needs of the resource system (install_data putting files into system-configured locations and packaging.database finding them); one of the thousand things mentioned in the “Status of Packaging” thread was an opinion by PJE that this was a bad choice, and even if I disagree (being a Debian guy and all :), a PEP would be in order to decide on such a big new functionality. Should these changes be reverted too? (I’d think yes.) |
Packaging removed in 576b8b182039. I’m going to wait an hour or two and in the absence of feedback will remove sysconfig.cfg too; that will be easy to revert if consensus was to keep it and I was not online (but I really think sysconfig.cfg should go). I’ll also look at the buildbots. |
Why are you removing packaging? |
Oh.. understand now packaging is being deferred. |
sysonfig.cfg removed in e989e7586da6. |
What is sysconfig.cfg? Keeping sysconfig is ok IMO. |
We should keep sysconfig imo |
These are the kind of questions from the top of my head which I think haven’t been hashed out. Or maybe it’s perfectly clear between Tarek and the few OS packagers that discussed this matter but there is no documentation of that. As the only client of the sysconfig.cfg file was packaging, I think the safe thing to do is to not add it in 3.3 and make it a part of the discussions for 3.4 (i.e. may need a PEP). |
Eric, ping? When can this be closed? |
packaging (and related changes in sysconfig) have been removed. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: