Mailman 3 August 2007 - Python-Dev

SF tracker closed now
by martin＠v.loewis.de Aug. 23, 2007

Aug. 23, 2007

We are starting with the tracker conversion. Please stop using the bug trackers (either SF or roundup) until further notice. Regards, Martin

1 0

Strange behavior of subprocess.Popen._get_handles under Windows
by Alexey Borzenkov Aug. 23, 2007

Aug. 23, 2007

For a long time I was surprised why if I have a script testme.py: import subprocess subprocess.call("echo Something", shell=True) and I try to execute it like this: python testme.py >testme.txt I get the output: The handle is invalid. Strange failures randomly happened with different programs, so I thought maybe this was intended (mis)behavior, and I found that I can workaround this by explicitly specifying std* handles: subprocess.call(...., stdin=sys.stdin, … [View More]

2 4

AtheOS/Syllable
by skip＠pobox.com Aug. 22, 2007

Aug. 22, 2007

The Syllable folks apparently still want to support Python, so I'm going to keep that support in there, switching "atheos" for "syllable" where it occurs. I have a patch against 2.5.1 from the Syllable folks. I'll see if I can make it apply to the trunk and py3k branches in a semi-clean fashion. Skip

1 0

Python 3000 Sprint @ Google
by Guido van Rossum Aug. 22, 2007

Aug. 22, 2007

It's official! The second annual Python Sprint @ Google is happening again: August 22-25 (Wed-Sat). We're sprinting at two locations, this time Google headquarters in Mountain View and the Google office in Chicago (thanks to Brian Fitzpatrick). We'll connect the two sprints with full-screen videoconferencing. The event is *free* and includes Google's *free gourmet food*. Anyone with a reasonable Python experience is invited to attend. The primary goal is to work on Python 3000, to polish off … [View More]

6 20

Re: [Python-Dev] [Python-3000] Documentation switch imminent
by Thomas Wouters Aug. 22, 2007

Aug. 22, 2007

On 8/14/07, Georg Brandl <g.brandl(a)gmx.net> wrote: > > Now that the converted documentation is fairly bug-free, I want to > make the switch. One thing I miss (and I haven't followed the discussions about the new layout at all, so I don't know if it came up already) is section numbers. I very often refer people to "Section 4.7 of the tutorial at docs.python.org/tut" or "Appendix B of the tutorial" or "Section 3.6.2 of the library reference", which the new layout doesn't … [View More]

4 9

How to interpret get_code from PEP 302?
by Brett Cannon Aug. 22, 2007

Aug. 22, 2007

PEP 302 ("New Import Hooks") has an optional extensions section so that tools like py2exe and py2app have an easier time. Part of the optional extensions is the method get_code that is to return the code object for the specified method (if the loader can handle it). But there is a lack in the definition of how get_code is supposed to be implemented. The definition says that the "method should return the code object associated with the module", which is fine. But then it goes on to state … [View More]

5 6

Re: [Python-Dev] backport new server-side SSL to older Pythons?
by Guido van Rossum Aug. 21, 2007

Aug. 21, 2007

On 8/21/07, Bill Janssen <janssen(a)parc.com> wrote: > I'd like to be able to backport this server-side SSL support to older > Pythons, like the 2.3.4 in CentOS 4 and the 2.3.5 in OS X 10.4. That would have to be a private fork or a 3rd party extension module; python.org is committed to keeping existing releases stable (feature-wise). > So I'd like to move all the SSL stuff out of the "socket" module, and > add a new top-level module called "ssl" (or "networking.ssl", or … [View More]

2 1

backport new server-side SSL to older Pythons?
by Bill Janssen Aug. 21, 2007

Aug. 21, 2007

I'd like to be able to backport this server-side SSL support to older Pythons, like the 2.3.4 in CentOS 4 and the 2.3.5 in OS X 10.4. So I'd like to move all the SSL stuff out of the "socket" module, and add a new top-level module called "ssl" (or "networking.ssl", or whatever the Py3K naming scheme says it should be). The socket module will then re-export a function from that module as socket.ssl(), which will continue to do exactly what it does now. More advanced users will call functions … [View More]

1 0

Re: [Python-Dev] How to interpret get_code from PEP 302?
by Phillip J. Eby Aug. 21, 2007

Aug. 21, 2007

At 11:22 AM 8/21/2007 -0700, Brett Cannon wrote: >This also means pkgutil is possibly non-compliant as it's get_code >implementation does the above suggestion (tries for source to avoid >timestamp check, and uses bytecode as backup). That's not actually true, it just *looks* that way. IIRC, mod_type will only be PY_SOURCE if there's no compiled version available. There's a different bug, though, which is that if you call get_code() on an ImpLoader when the module hasn't been … [View More]

1 0

RFC - proposal for urilib. unified module of urlparse, urllib and urllib2
by O.R.Senthil Kumaran Aug. 21, 2007

Aug. 21, 2007

Hello All, I am drafting a PEP proposing a module 'urilib', which will be the unified module of urlparse, urllib and urllib2. a) _all_ functions will include from urlparse,urllib and urllib2. b) overlapping functionality between urllib and urllib2 to be ironed out. c) RFC3986 and RFC3987 compliant. Cleanup task of urllib was my G-SoC, and this unified module is a suggestion with python 2.6 in mind. I would like to know your thoughts on - How should we plan to maintain the backward … [View More]

3 2