RetroSearch Browse

Mon Aug 25 12:50:45 EDT 2003 · https://mail.python.org/pipermail/python-dev/2003-August/037789.html

On Monday, August 25, 2003, at 06:36 AM, Guido van Rossum wrote:
> Well, in standard Python, the only access to the system is *also*
> through extension modules -- if you count __builtin__ as an extension
> module.  The other extension module you want to avoid is the posix
> module (under Windows, the nt module).  It should be a simple matter
> to remove this from your module search path.

No, it isn't: simply doing "open = type(sys.stdout)" will revive open
for you. So you'd really have to make sure no file objects are 
accessible
either. And there's lots more loopholes like this.

With the current type system I think the only real solution would be
to block this at a very low level, i.e. removing file objects from your
build, or at least completely disabling their side-effects.
--
Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-August/037789.html below:

[Python-Dev] Embedded python module search path