This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients asvetlov, barry, brett.cannon, christian.heimes, eric.araujo, lemburg, mdengler, ncoghlan, pitrou, vstinner, yaccz
Date 2013-06-20.15:15:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7dvremWQ5GOn_728BqGH9jRAyRdrRPzQX9=8DHxyw75mA@mail.gmail.com>
In-reply-to <1371739211.73.0.15225009249.issue16499@psf.upfronthosting.co.za>
Content
CPython's startup sequence and collection of global flags are organically
evolved madness, so I think adding even more complexity to them is a bad
idea. When you're in a hole, the first thing to do is *stop digging*.

I could use help laying the foundations for PEP 432 though - getting the
separate Programs directory split out, breaking up the monstrosity that is
pythonrun.c, etc. Implementing that basic refactoring in default will make
it more feasible to keep the PEP branch up to date without major conflicts.
On 21 Jun 2013 00:40, "Christian Heimes" <report@bugs.python.org> wrote:

>
> Christian Heimes added the comment:
>
> It comes from Nick and http://www.python.org/dev/peps/pep-0432/ . Once
> PEP 432 is in place we can easily create variants of Python binaries with
> special flags.
>
> I'm in favor with python -I, too.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue16499>
> _______________________________________
>
History
Date User Action Args
2013-06-20 15:15:41ncoghlansetrecipients: + ncoghlan, lemburg, barry, brett.cannon, pitrou, vstinner, christian.heimes, eric.araujo, asvetlov, mdengler, yaccz
2013-06-20 15:15:41ncoghlanlinkissue16499 messages
2013-06-20 15:15:40ncoghlancreate