Re: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source

At 05:26 PM 9/27/2006 -0700, Brett Cannon wrote: >Ah, OK. So for importing 'email', the zipimporter would call the .pyc >importer and it would ask the zipimporter, "can you get me email.pyc?" and >if it said no it would move on to asking the .py importer for email.py, etc. Yes, exactly. >That

Re: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source

On 9/27/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: At 04:11 PM 9/27/2006 -0700, Brett Cannon wrote:>On 9/27/06, Phillip J. Eby><[EMAIL PROTECTED]>[EMAIL PROTECTED] > wrote:>>At 02:11 PM 9/27/2006 -0700, Brett Cannon wrote:>> >But it has been suggested here that the import machinery be rewritten

Re: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source

At 04:11 PM 9/27/2006 -0700, Brett Cannon wrote: >On 9/27/06, Phillip J. Eby ><[EMAIL PROTECTED]> wrote: >>At 02:11 PM 9/27/2006 -0700, Brett Cannon wrote: >> >But it has been suggested here that the import machinery be rewritten in >> >Python. Now I have never touched

Re: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source

On 9/27/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: At 02:11 PM 9/27/2006 -0700, Brett Cannon wrote:>But it has been suggested here that the import machinery be rewritten in>Python.  Now I have never touched the import code since it has always had>the reputation of being less than friendly to wor

Re: [Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source

At 02:11 PM 9/27/2006 -0700, Brett Cannon wrote: >But it has been suggested here that the import machinery be rewritten in >Python. Now I have never touched the import code since it has always had >the reputation of being less than friendly to work with. I am asking for >opinions from people w

[Python-Dev] difficulty of implementing phase 2 of PEP 302 in Python source

I am at the point with my security work that I need to consider how I am going to restrict importing modules.  My current plan is to basically implement phase 2 of PEP 302 and control imports through what importer objects are provided.  This work should lead to a meta_path importer for built-ins an

Re: [Python-Dev] Minipython

> I would like to run Python scripts on an embedded MIPS Linux platform > having only 2 MiB of flash ROM and 16 MiB of RAM for everything. (...) Have you looked at Python for S60 and Python for the Maemo platform? If not directly useful, they should provide some hints. [1] http://opensource.noki

Re: [Python-Dev] List of candidate 2.4.4 bugs?

A.M. Kuchling schrieb: > One reason I often don't backport a bug is because I'm not sure if > there will be another bugfix release; if not, it's wasted effort, and > I wasn't sure if a 2.4.4 release was ever going to happen. After > 2.4.4, will there be a 2.4.5 or is that too unlikely? The "tradi

Re: [Python-Dev] openssl - was: 2.4.4c1 October 11, 2.4.4 final October 18

Jim Jewett schrieb: > OpenSSL should probably be upgraded to 0.9.8.c (or possibly 0.9.7.k) > because of the security patch. > >http://www.openssl.org/ >http://www.openssl.org/news/secadv_20060905.txt > > I'm not sure which version shipped with the 2.4 windows binaries, but > externals (fo

[Python-Dev] openssl - was: 2.4.4c1 October 11, 2.4.4 final October 18

OpenSSL should probably be upgraded to 0.9.8.c (or possibly 0.9.7.k) because of the security patch. http://www.openssl.org/ http://www.openssl.org/news/secadv_20060905.txt I'm not sure which version shipped with the 2.4 windows binaries, but externals (for 2.5) still points to 0.9.8.a, wh

Re: [Python-Dev] 2.4.4c1 October 11, 2.4.4 final October 18

Fredrik> [EMAIL PROTECTED] wrote: >> I think the right thing is for InteractiveConsole to dup >> sys.std{in,out,err} and do its own thing for its raw_input() method >> instead of naively calling the raw_input() builtin. Fredrik> what guarantees that sys.stdin etc has a valid a

Re: [Python-Dev] 2.4.4c1 October 11, 2.4.4 final October 18

[EMAIL PROTECTED] wrote: > I think the right thing is for InteractiveConsole to dup sys.std{in,out,err} > and do its own thing for its raw_input() method instead of naively calling > the raw_input() builtin. what guarantees that sys.stdin etc has a valid and dup:able fileno when the console is i

Re: [Python-Dev] List of candidate 2.4.4 bugs?

On Wed, Sep 27, 2006 at 06:56:14PM +0200, "Martin v. Löwis" wrote: > I don't think so. Also, I see little chance that many bugs will be fixed > that aren't already. People should really do constant backporting, > instead of starting backports when a subminor release is made. Agreed. One reason

Re: [Python-Dev] List of candidate 2.4.4 bugs?

A.M. Kuchling schrieb: > Is anyone maintaining a list of candidate bugs to be fixed in 2.4.4? I don't think so. Also, I see little chance that many bugs will be fixed that aren't already. People should really do constant backporting, instead of starting backports when a subminor release is made.

[Python-Dev] List of candidate 2.4.4 bugs?

Is anyone maintaining a list of candidate bugs to be fixed in 2.4.4? If not, should we start a wiki page for the purpose? --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mai

[Python-Dev] [SECUNIA] "buffer overrun in repr() for unicode strings" Potential Vulnerability (fwd)

This came in to the webmaster address and was also addressed to a number of individuals (looks like the SF project admins). This appears like it would be of general interest to this group. Looking through this message and the various bug tracker items it's not clear to me if Secunia wants to kno

Re: [Python-Dev] 2.4.4c1 October 11, 2.4.4 final October 18

Anthony> If you know of any backports that should go in, please make Anthony> sure you get them done before the 11th. skip> John Hunter (matplotlib author) recently made me aware of a skip> problem with code.InteractiveConsole. It doesn't protect itself skip> from the user cl