Mailman 3 November 2005 - Python-Dev

Short-circuiting iterators
by Matthew F. Barnes Nov. 30, 2005

Nov. 30, 2005

Hello, I've not had much luck in searching for a discussion on this in the Python-Dev archives, so bear with me. I had an idea this morning for a simple extension to Python's iterator protocol that would allow the user to force an iterator to raise StopIteration on the next call to next(). My thought was to add a new method to iterators called stop(). In my situation it would be useful as a control-flow mechanism, but I imagine there are many other use cases for it: generator = … [View More]

2 2

Re: [Python-Dev] Metaclass problem in the "with" statement semantics in PEP 343
by Edward Loper Nov. 30, 2005

Nov. 30, 2005

Michael Chermside wrote: >> Right now, we say that there's one rule for all *normal* attributes >> and >> methods, and a slightly different rule for all double-underbar >> methods. Guido responded: > But it's not normal vs. __xyzzy__. A specific set of slots (including > next, but excluding things like __doc__) get special treatment. The > rest don't. All I'm saying is that I don't care to give __context__ > this special treatment. Perhaps we should … [View More]

2 1

Re: [Python-Dev] Metaclass problem in the "with" statement semantics in PEP 343
by Michael Chermside Nov. 29, 2005

Nov. 29, 2005

Nick writes: > I think we need to fix the proposed semantics so that they access the slots > via the type, rather than directly through the instance. Otherwise the slots > for the with statement will behave strangely when compared to the slots for > other magic methods. Guido writes: > I can't make myself care > about this. The code is broken. You get an error message. Nick writes: > The bit that more concerns me is the behavioural discrepancy that comes from > having … [View More]

2 1

Metaclass problem in the "with" statement semantics in PEP 343
by Nick Coghlan Nov. 29, 2005

Nov. 29, 2005

Given the current semantics of PEP 343 and the following class: class null_context(object): def __context__(self): return self def __enter__(self): return self def __exit__(self, *exc_info): pass Mistakenly writing: with null_context: # Oops, passed the class instead of an instance Would give a less than meaningful error message: TypeError: unbound method __context__() must be called with null_context instance as first argument … [View More]

3 3

CVS repository mostly closed now
by "Martin v. Löwis" Nov. 29, 2005

Nov. 29, 2005

I tried removing the CVS repository from SF; it turns out that this operation is not supported. Instead, it is only possible to remove it from the project page; pserver and ssh access remain indefinitely, as does viewcvs. The recommended procedure is to place a file into the repository indicating the repository has moved; this is what I just did. Regards, Martin

4 4

reference leaks
by Neal Norwitz Nov. 28, 2005

Nov. 28, 2005

There are still a few reference leaks I've been able to identify. I didn't see an obvious solution to these (well, I saw one obvious solution which crashed, so obviously I was wrong). When running regrtest with -R here are the ref leaks reported: test_codeccallbacks leaked [2, 2, 2, 2] references test_compiler leaked [176, 242, 202, 248] references test_generators leaked [254, 254, 254, 254] references test_tcl leaked [35, 35, 35, 35] references test_threading_local leaked [36, 36, 28, 36] … [View More]

4 5

Patch Req. # 1351020 & 1351036: PythonD modifications
by decker＠dacafe.com Nov. 28, 2005

Nov. 28, 2005

Hello, I would appreciate feedback concerning these patches before the next "PythonD" (for DOS/DJGPP) is released. Thanks in advance. Regards, Ben Decker Systems Integrator http://www.caddit.net ----------------------------------------- Stay ahead of the information curve. Receive MCAD news and jobs on your desktop daily. Subscribe today to the MCAD CafeNews newsletter. [ http://www10.mcadcafe.com/nl/newsletter_subscribe.php ] It's informative and essential.

5 12

Bug day this Sunday?
by A.M. Kuchling Nov. 28, 2005

Nov. 28, 2005

Is anyone interested in joining a Python bug day this Sunday? A useful task might be to prepare for the python-core sprint at PyCon by going through the bug and patch managers, and listing bugs/patches that would be good candidates for working on at PyCon. We'd meet in the usual location: #python-dev on irc.freenode.net, from roughly 9AM to 3PM Eastern (2PM to 8PM UTC) on Sunday Dec. 4. --amk

1 0

Re: [Python-Dev] SRE should release the GIL (was: no subject)
by Duncan Grisby Nov. 28, 2005

Nov. 28, 2005

On Monday 28 November, Guido van Rossum wrote: > On 11/24/05, Duncan Grisby <duncan-pythondev(a)grisby.org> wrote: > > I have encountered a problem with the re module. I have a > > multi-threaded program that does lots of regular expression searching, > > with some relatively complex regular expressions. Occasionally, events > > can conspire to mean that the re search takes minutes. That's bad > > enough in and of itself, but the real problem is that the … [View More]

1 0

(no subject)
by Duncan Grisby Nov. 28, 2005

Nov. 28, 2005

Hi, I posted this to comp.lang.python, but got no response, so I thought I would consult the wise people here... I have encountered a problem with the re module. I have a multi-threaded program that does lots of regular expression searching, with some relatively complex regular expressions. Occasionally, events can conspire to mean that the re search takes minutes. That's bad enough in and of itself, but the real problem is that the re engine does not release the interpreter lock while it is … [View More]

6 6