[Python-Dev] Accepting PEP 587 (Python Initialization Configuration)
Thomas Wouters
thomas at python.org
Sun May 26 10:02:21 EDT 2019
More information about the Python-Dev mailing list
Sun May 26 10:02:21 EDT 2019
- Previous message (by thread): [Python-Dev] PEP 594 -- Bundling libraries?
- Next message (by thread): [Python-Dev] Accepting PEP 587 (Python Initialization Configuration)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
As PEP-delegate, I'm accepting version 5 of PEP 587 (Python Initialization Configuration). I don't think Victor has posted the latest version, but it contains a couple of minor renames, and a new private API to allow us to experiment with two-phase initialisation of Python. There's still time to debate exact names and work on the wording of the PEP, but I'm satisfied the design is solid, a clear improvement over what we currently have, and a step in the right direction for some of the more extensive changes that have been proposed (e.g. using Python *code* for the Python configuration. If we do get to that point, the PEP contains a few things that are superfluous, but I'd consider them minor transitionary warts at that point -- if we ever get there). Thanks, Victor, for pushing this massive amount of work through; it won't affect most people using Python (at least until the rest of PEP 432 lands) but it's a giant boon to those of us who embed Python :) -- Thomas Wouters <thomas at python.org> Hi! I'm an email virus! Think twice before sending your email to help me spread! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190526/09efcbe8/attachment-0001.html>
- Previous message (by thread): [Python-Dev] PEP 594 -- Bundling libraries?
- Next message (by thread): [Python-Dev] Accepting PEP 587 (Python Initialization Configuration)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list