On 25 Jul 2014 03:51, "Brett Cannon" wrote:
> The problem with all of this is you are essentially asking for a hook to
let you have code have access to the interpreter state before it is fully
initialized. Zipimport and the various bits of code that get loaded during
startup are special since the
On Thu Jul 24 2014 at 2:12:20 PM, Phil Thompson
wrote:
> On 24/07/2014 6:48 pm, Brett Cannon wrote:
> > On Thu Jul 24 2014 at 1:07:12 PM, Phil Thompson
> >
> > wrote:
> >
> >> I have an importer for use in applications that embed an interpreter
> >> that does a similar job to the Zip importer (e
On 24/07/2014 6:48 pm, Brett Cannon wrote:
On Thu Jul 24 2014 at 1:07:12 PM, Phil Thompson
wrote:
I have an importer for use in applications that embed an interpreter
that does a similar job to the Zip importer (except that the storage
is
a C data structure rather than a .zip file). Just lik
On Thu Jul 24 2014 at 1:07:12 PM, Phil Thompson
wrote:
> I have an importer for use in applications that embed an interpreter
> that does a similar job to the Zip importer (except that the storage is
> a C data structure rather than a .zip file). Just like the Zip importer
> I need to import my i
I have an importer for use in applications that embed an interpreter
that does a similar job to the Zip importer (except that the storage is
a C data structure rather than a .zip file). Just like the Zip importer
I need to import my importer and add it to sys.path_hooks. However the
earliest op
