Mailman 3 July 2004 - Python-Dev

String literals escape sequences
by orbitz July 9, 2004

July 9, 2004

The python language reference says: " Unlike Standard C, all unrecognized escape sequences are left in the string unchanged, i.e., /the backslash is left in the string/. (This behavior is useful when debugging: if an escape sequence is mistyped, the resulting output is more easily recognized as broken.)" It seems to me that a syntax error of some kind would be even more useful. For instance if one is dealing with an extremely large output they might be able to miss a single missing \t … [View More]

2 1

Re: [Python-Dev] VC 7.1 maintenance?
by M.-A. Lemburg July 9, 2004

July 9, 2004

Tim Peters wrote: > [Guido] > >>Is anybody maintaining the project files for Visual Studio 7.1? > > Martin, Thomas and I all fiddle it when we notice it needs something. I > view Martin as being the primary owner. Are we going to have a VC7.1 binary of Python 2.4 for Windows ? (Just asking whether it's time to finally open the VC7 shrink- wrap box ;-) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 16 2004) >… [View More]

5 11

bug in httplib.HTTPResponse.read() ?
by Mihai Ibanescu July 9, 2004

July 9, 2004

Hello, Can someone with more experience with httplib have a look at this? https://sourceforge.net/tracker/index.php?func=detail&aid=988120&group_id=5… Am I right that this is indeed a bug? Thanks, Misa

1 0

Possible problem with recent weakref or bsddb changes
by Skip Montanaro July 9, 2004

July 9, 2004

Greg checked in some changes to bsddb on June 28. Fred checked in some changes to weakref on July 2. One or both I think conspired to break Spambayes for me. I filed a bug report a couple days ago <http://python.org/sf/986528> and originally assigned it to Greg. I just switched it to Fred since his changes were more recent and seemed more wide ranging. I just reversed those changes in my sandbox and am building now to see if it solves my problem. Might be something to pay close … [View More]

2 1

collecting 2.4 highlights
by Anthony Baxter July 9, 2004

July 9, 2004

There's a first go at a 2.4 'highlights' page on the website now. I'm absolutely positive that I missed some - I was working from the whatsnew document, but that's missing a lot. I plan to go through the Misc/NEWS document between now and a2 and add more, but if there's something you feel should be there, feel free to either add it (if you have pydotorg checkin privs) or else email me... Anthony -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

2 1

New test failure, test_socket, WinXP
by Tim Peters July 9, 2004

July 9, 2004

Fails every time, in release and debug builds: test test_socket failed -- Traceback (most recent call last): File "C:\Code\python\lib\test\test_socket.py", line 311, in testGetServBy eq(socket.getservbyport(port2), service) AssertionError: 'http' != 'www'

6 12

Re: [Python-Dev] decimal.py signals & traps
by mcherm＠mcherm.com July 9, 2004

July 9, 2004

Raymond writes: > I would like change the Context constructor API to [...] > (list only the flags and traps that you want set). +1 > The dictionaries themselves would be made private (allowing them to > be recast as sets if desired). +1 David writes: > The point of this discussion and the patch is that according to the > spec and PEP 327, there *is no* "conversion syntax" signal. > "Conversion syntax" is an exceptional *condition*, which triggers the > "invalid-… [View More]

1 0

decimal.py signals & traps
by David Goodger July 8, 2004

July 8, 2004

There's a problem in the decimal.py API regarding signals & traps. I noticed Raymond's checkin enabling certain traps (thanks Raymond!), so I updated my copy and played around a bit: >>> from decimal import Decimal >>> Decimal('1')/0 Traceback (most recent call last): ... decimal.DivisionByZero: x / 0 As expected. But: >>> Decimal('0')/0 Decimal("NaN") I expected this to raise decimal.DivisionUndefined. Even worse: >>> Decimal('bogus') Decimal(… [View More]"NaN") That should have raised decimal.ConversionSyntax. This behavior obviously doesn't agree with: [Tim Peters] > You can't get a NaN or infinity from finite operands without > signaling one of the 3 I recommend trap-enabling, so enabling those > traps stops their program the instant the first NaN or infinity > appears. The problem is that the implementation associates traps with what it calls "signals" but the spec & PEP 327 call "conditions". I believe that led to a misunderstanding: [Tim Peters] > I'm still of the opinion that the invalid-operation, overflow, and > division-by-zero traps should be enabled by default, and the others > disabled Tim is referring to traps associated with spec/PEP-defined "signals". Raymond implemented the default-enabled traps like this: _default_traps.update( {DivisionByZero:1, Overflow:1, InvalidOperation:1}) Take a look at the "Signal" column of the table in <http://www.python.org/peps/pep-0327.html#exceptional-conditions>. The "invalid-operation" *signal* is associated with 5 different *conditions*: conversion syntax, division impossible, division undefined, invalid context, and invalid operation. The spec/PEP lists 12 conditions and 8 signals, but >>> len(decimal.Signals) 13 decimal.Signals is actually a list of spec/PEP *conditions*, with decimal.DecimalException (the base exception class) also included. The easy solution is to change _default_traps.update( {DivisionByZero:1, Overflow:1, InvalidOperation:1}) to _default_traps.update( {DivisionByZero:1, Overflow:1, InvalidOperation:1, ConversionSyntax:1, DivisionImpossible:1, DivisionUndefined:1, InvalidContext}) But I don't think that's the best solution. It still leaves the mismatch between spec/PEP "signals" and implementation "signals". Should traps be set on spec/PEP conditions, or spec/PEP signals? If the former, decimal.Signals should at least be renamed to decimal.Conditions. If the latter, decimal.py's implementation of exceptions needs to be reworked. -- David Goodger <http://python.net/~goodger> [View Less]

3 4

Make PyType_GenericNew and object_new the same
by Jim Fulton July 8, 2004

July 8, 2004

At one time, object's tp_new slot was filled with PyType_GenericNew. Later, someone decided to add a sanity check to object's new that raises an exception if arguments are passed and __init__ was interited from object. (object's __init__ takes no arguments.) At this point, objects's tp_new became different from PyType_GenericNew. Now, I have some C types that are meant to be used as mix-in classes. I have to provide a tp_new slot filler if I want these classes (or their subclasses) to be … [View More]

1 0

2.4a1
by Anthony Baxter July 8, 2004

July 8, 2004

I plan to start attempting to get a 2.4a1 out the door in the morning my time. Depending on how that goes, it will either be then, or on the Friday - I'll post updates when I see how it's going. Given we have a couple of bits that haven't landed yet (such as decorators) I suspect we're probably looking at about 3 alpha releases - I'm thinking 2-3 weeks between them. I'd love to get feedback on this - I'll write up the release plan once I hear back from people. I'm not too fussed about the … [View More]

6 7