This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients DazWorrall, alex, brian.curtin, carljm, coderanger, dabeaz, eric.smith, flox, jhylton, karld, kevinwatters, loewis, mahmoudimus, nirai, pitrou, rcohen, rh0dium, tarek
Date 2010-03-16.01:22:07
SpamBayes Score 0.055108
Marked as misclassified No
Message-id <20100315212200.0066f16d@msiwind>
In-reply-to <1268702028.29.0.284712997798.issue7946@psf.upfronthosting.co.za>
Content
> Oh the situation definitely matters.   Although, in the big picture,
> most programmers would probably prefer to have fast I/O performance
> over slow I/O performance :-).

Yes, of course. But that's not the point. We could try to improve GIL
behaviour in every thinkable situation, at the expense of code
complexity. But we don't want to make the code too complex and
delicate to maintain, and that's why I've asked for advice on
python-dev.
History
Date User Action Args
2010-03-16 01:22:09pitrousetrecipients: + pitrou, loewis, jhylton, eric.smith, kevinwatters, tarek, karld, carljm, coderanger, nirai, alex, brian.curtin, flox, DazWorrall, rh0dium, rcohen, dabeaz, mahmoudimus
2010-03-16 01:22:08pitroulinkissue7946 messages
2010-03-16 01:22:07pitroucreate