Message89109
| Author |
lowell87 |
| Recipients |
Frans, lowell87, mramahi77, neyro, rcronk, vinay.sajip |
| Date |
2009年06月08日.20:27:44 |
| SpamBayes Score |
9.639933e-06 |
| Marked as misclassified |
No |
| Message-id |
<839ec5810906081327u2b2a535bl84e516adfd615d95@mail.gmail.com> |
| In-reply-to |
<1244490352.82.0.676341337077.issue4749@psf.upfronthosting.co.za> |
| Content |
I tested this against a number of different python installs that I
have laying around. Here are the results that I found:
Releases that reproduce this bug:
Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32
Python 2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC v.1310 32 bit (Intel)] on win32
Python 2.4.5 (#2, Jul 31 2008, 18:51:48) [GCC 4.2.3 (Ubuntu
4.2.3-2ubuntu7)] on linux2 (Ubuntu 8.04)
Python 2.4.6 (#2, Mar 19 2009, 10:00:53) [GCC 4.3.3] on linux2 (Ubuntu 9.04)
Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit
(Intel)] on win32
The following release worked fine:
Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52) [GCC 4.2.3 (Ubuntu
4.2.3-2ubuntu7)] on linux2 (Ubuntu 8.04)
Python 2.5.4 (r254:67916, Apr 4 2009, 17:55:16) [GCC 4.3.3] on linux2
(Ubuntu 9.04)
Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41) [GCC 4.3.3] on
linux2 (Ubuntu 9.04) |
|