[Python-Dev] is sys.modules not meant to be replaced? (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Jul 25 07:33:09 CEST 2011
- Previous message: [Python-Dev] is sys.modules not meant to be replaced?
- Next message: [Python-Dev] is sys.modules not meant to be replaced?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jul 25, 2011 at 2:50 PM, Eric Snow <ericsnowcurrently at gmail.com> wrote:
I agree with what you are saying wholeheartedly, but still think there is something fishy with the way that sys.modules works. I'll take it from here to a tracker issue though. :)
Yup - the import system has a whole mess of interrelated global state that really needs to be on a class that can use descriptors to correctly invalidate caches when attributes are mutated or rebound.
The ImportEngine GSoC project is the first step along the long, winding path towards doing something about that :)
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] is sys.modules not meant to be replaced?
- Next message: [Python-Dev] is sys.modules not meant to be replaced?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]