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 benjamin.peterson, brett.cannon, eric.snow, ncoghlan, pitrou
Date 2012-04-18.22:06:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334786788.24.0.728671121253.issue12598@psf.upfronthosting.co.za>
In-reply-to
Content
It's about navigability/discovery of the source - to find out how the sys module gets initialised, you currently have to look in multiple places. The idea of the patch is to simplify that to the one logical place: sysmodule.c

However, I'm not sure it's right to actually *move* the full import state initialisation. A simple *indirection* (pythonrun.c -> sysmodule.c -> import.c) would solve the navigability problem while also retaining some level of encapsulation for the import state initialisation.
History
Date User Action Args
2012-04-18 22:06:28ncoghlansetrecipients: + ncoghlan, brett.cannon, pitrou, benjamin.peterson, eric.snow
2012-04-18 22:06:28ncoghlansetmessageid: <1334786788.24.0.728671121253.issue12598@psf.upfronthosting.co.za>
2012-04-18 22:06:27ncoghlanlinkissue12598 messages
2012-04-18 22:06:27ncoghlancreate