Re: [Python-Dev] New methods for weakref.Weak*Dictionary types

2006-05-10 Thread Armin Rigo
Hi Tim, On Mon, May 01, 2006 at 04:57:06PM -0400, Tim Peters wrote: > """ > # Return a list of weakrefs to all the objects in the collection. > # Because a weak dict is used internally, iteration is dicey (the > # underlying dict may change size during iteration, due to gc or > # a

Re: [Python-Dev] New methods for weakref.Weak*Dictionary types

2006-05-10 Thread Tim Peters
[Tim Peters] >> """ >> # Return a list of weakrefs to all the objects in the collection. >> # Because a weak dict is used internally, iteration is dicey (the >> # underlying dict may change size during iteration, due to gc or >> # activity from other threads). [Armin Rigo] > But th

Re: [Python-Dev] [Python-checkins] r45925 - in python/trunk: Lib/tempfile.py Lib/test/test_os.py Misc/NEWS Modules/posixmodule.c

2006-05-10 Thread Martin v. Löwis
M.-A. Lemburg wrote: > I've tried to find documentation on _dosmaperr() but there's > nothing on MSDN. Is this an official API ? No. It always was undocumented, and apparently intentionally so (both the API, and the precise details of the mapping). > FWIW, this is the official system error code t

Re: [Python-Dev] [Python-checkins] r45925 - in python/trunk: Lib/tempfile.py Lib/test/test_os.py Misc/NEWS Modules/posixmodule.c

2006-05-10 Thread M.-A. Lemburg
Martin v. Löwis wrote: > I'm saying that changing WindowsError to include set errno > to DOS error codes would *also* be an incompatible change. > >> Since code catching IOError will also see any WindowsError >> exception, I'd opt for making .errno always return the >> DOS/BSD error codes and have

Re: [Python-Dev] [Python-checkins] r45925 - in python/trunk: Lib/tempfile.py Lib/test/test_os.py Misc/NEWS Modules/posixmodule.c

2006-05-10 Thread Martin v. Löwis
M.-A. Lemburg wrote: > BTW, and intended as offer for compromise, should we instead > add the Win32 codes to the errno module (or a new winerrno > module) ?! I can write a parser that takes winerror.h and > generates the module code. Instead won't help: the breakage will still occur. It would be p

Re: [Python-Dev] 2.5 open issues

2006-05-10 Thread Michael Hudson
"Neal Norwitz" <[EMAIL PROTECTED]> writes: > Here's what's left for 2.5 after the most recent go around. > > There's no owner for these items. If no one takes them, they won't > get done and I will move them to deferred within a week: > > * Add @decorator decorator to functional, rename to func

[Python-Dev] nag, nag -- 2.5 open issues

2006-05-10 Thread Neal Norwitz
If you are addressed on this message, it means you have open issues that need to be resolved for 2.5. Some of these issues are documentation, others are code issues. This information comes from PEP 356. The best way to get me to stop bugging you is to close out these tasks. :-) Note the next al