Author lemburg
Recipients Arfrever, brett.cannon, eric.smith, eric.snow, lemburg, ncoghlan, pitrou
Date 2012-04-24.17:37:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <4F96E4B9.9030208@egenix.com>
In-reply-to <1335280219.42.0.834697229717.issue14657@psf.upfronthosting.co.za>
Content
test me
thod. Another option is we hide the source as _importlib or something to allow direct importation w/o any tricks under a protected name.

Using the freeze everything approach you make things easier for the
implementation, since you don't have to think about whether certain
pieces of code are already available or not.

For development, you can also have the package load bytecode
or source from an external package instead of running (all of)
the module's bytecode that was compiled into the binary.

This is fairly easy to do, since the needed exec() does not
depend on the import machinery.

The only downside is big if statement to isolate the frozen
version from the loaded one - would be great if we had a
command to stop module execution or code execution for a block to
make that more elegant, e.g. "break" at module scope :-)
History
Date User Action Args
2012-04-24 17:37:01lemburgsetrecipients: + lemburg, brett.cannon, ncoghlan, pitrou, eric.smith, Arfrever, eric.snow
2012-04-24 17:37:00lemburglinkissue14657 messages
2012-04-24 17:37:00lemburgcreate