Message130189
Thanks for the comment. It's my first patch. :-)
> - the patch doesn't apply on Python 3.3
That latest patch file I generated against the tip of 3.1 branch. Should I create two separate patches for 3.1 and 3.2+ (which will apply on 3.3, as well)? Actually, this crash will reproduce on (from my testing) 2.7 with "-u" option on, as well...
> - I don't want to commit the tests because they write 66000 * 2 characters to the test output, which floods the test output. I don't know how to create a fake stdout which is a TTY but not the real stdout, especially on Windows. I think that manual tests only once should be enough. Or does anyone know how to create a fake TTY output?
I have a few ideas to work around this and still have a unit test... |
|
Date |
User |
Action |
Args |
2011-03-06 20:46:08 | santoso.wijaya | set | recipients:
+ santoso.wijaya, terry.reedy, amaury.forgeotdarc, pitrou, vstinner, casevh, neologix |
2011-03-06 20:46:08 | santoso.wijaya | set | messageid: <1299444368.29.0.139096032965.issue11395@psf.upfronthosting.co.za> |
2011-03-06 20:46:07 | santoso.wijaya | link | issue11395 messages |
2011-03-06 20:46:07 | santoso.wijaya | create | |
|