Message 106782 - Python tracker

➜

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	gregory.p.smith
Recipients	DazWorrall, Michele, aconrad, alex, andrix, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, jcea, jhylton, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, ncoghlan, neologix, nirai, pitrou, portante, rcohen, rh0dium, tarek, thouis, victorpoluceno, ysj.ray
Date	2010-05-30.21:44:33
SpamBayes Score	0.035160854
Marked as misclassified	No
Message-id	<1275255875.68.0.823881104436.issue7946@psf.upfronthosting.co.za>
In-reply-to

Content
Thanks for all your work Nir! I personally think the BFS approach is the best we've seen yet for this problem! Having read the thread you linked to in full (ignoring the tagents bikeshedding and mudslinging that went on there), it sounds like the general consensus is that we should take thread scheduling changes slowly and let the existing new implementation bake in the 3.2 release. That puts this issue as a possibility for 3.3 if users demonstrate real world application problems in 3.2. (personally I'd say it is already obvious that there are problems an wde should go ahead with your BFS based approach but realistically the we're still better off in 3.2 than we were in 3.1 and 2.x as is)

Thanks for all your work Nir!  I personally think the BFS approach is the best we've seen yet for this problem!

Having read the thread you linked to in full (ignoring the tagents  bikeshedding and mudslinging that went on there), it sounds like the general consensus is that we should take thread scheduling changes slowly and let the existing new implementation bake in the 3.2 release.  That puts this issue as a possibility for 3.3 if users demonstrate real world application problems in 3.2.

(personally I'd say it is already obvious that there are problems an wde should go ahead with your BFS based approach but realistically the we're still better off in 3.2 than we were in 3.1 and 2.x as is)

History
Date	User	Action	Args
2010-05-30 21:44:35	gregory.p.smith	set	recipients: + gregory.p.smith, loewis, jhylton, jcea, ncoghlan, pitrou, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, durin42, eric.araujo, nirai, alex, andrix, konryd, brian.curtin, victorpoluceno, flox, DazWorrall, cool-RR, rh0dium, rcohen, dabeaz, mahmoudimus, portante, aconrad, ysj.ray, neologix, thouis, donaldjeo, Michele
2010-05-30 21:44:35	gregory.p.smith	set	messageid: <1275255875.68.0.823881104436.issue7946@psf.upfronthosting.co.za>
2010-05-30 21:44:33	gregory.p.smith	link	issue7946 messages
2010-05-30 21:44:33	gregory.p.smith	create