Regarding the recent test_ssl.py failures in py3k; I'm at a loss as to what the py3k version should look like in comparison to trunk. At the moment, there are pretty significant differences. I played around with just copying the trunk version into py3k and running 2to3, but that yielded significantly more errors than there is currently being thrown.
Trying to review the svn logs for both the trunk and py3k versions was difficult to say the least -- the myriad of svnmerge information certainly made it hard to figure out the point at which the two files digressed so much, at least in the 10-15m I spent on it. Bill, can you offer any insight? Are the two versions meant to have diverged so much? > -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > rg] On Behalf Of Trent Nelson > Sent: 09 April 2008 13:24 > To: Christian Heimes; [EMAIL PROTECTED]; Python 3000 > Subject: Re: [Python-checkins] [Python-3000] buildbot failure > in ppc Debian unstable 3.0 > > > > I can't run the ssl tests with -unetwork on my machine. > Could somebody > > please fix the test for me? > > Oeer. The write() issues are easily fixed w/ b''. > Investigating the lack of AsyncoreHTTPSServer, though, > yielded quite significant differences between the trunk and > py3k versions of test_ssl.py. If no-one beats me to it I'll > look at fixing it over lunch (in an hour or so). > > Trent. > _______________________________________________ > Python-checkins mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/python-checkins > _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
