On 4/4/06, Thomas Wouters <thomas at python.org> wrote: > > > On 4/4/06, Jean-Paul Calderone <exarkun at divmod.com> wrote: > > > > Of course anyone who is interested can run the Twisted test suite very > easily and take a look at the failures themselves (if you have Twisted > installed, "trial twisted" will do it). > > > ... and can guess which errors/failures are specific to Python 2.5 (for > instance, the lack of PyCrypto in my 2.5-alpha install generates a lot of > failures.) My AMD64 machine was giving a _lot_ of errors on > zip(xrange(sys.maxint), iterable), which I now fixed in trunk. I'm > re-running the tests to find out which ones are left over, but I'm having a > hard time figuring out what to look at in trial's rather verbose logfile. > There seem to be quite a few tracebacks involving Exception subclasses, in > any case. Perhaps changing Exception's type in 2.5 wasn't a good idea after > all (but hey, that's what alphas are for ;) No, the idea was a wonderful idea! =) Are the errors because of something in Python, or because Twisted has not been changed to handle the new semantics? I know so far test failures have come from people making overly strict assumptions about the output (e.g., I think it was Thomas or Greg who was getting failures because ``type(Exception)`` outputted a different string for doctest stuff). Is that the case here? -Brett > > Oh, goodie, a segmentation fault. Let's see if I can reproduce it ;P > > > -- > Thomas Wouters < thomas at python.org> > > Hi! I'm a .signature virus! copy me into your .signature file to help me > spread! > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/brett%40python.org > > >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4