Message 347640 - 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.

In-reply-to
Author	gregory.p.smith
Recipients	DazWorrall, Dima.Tisnek, Michele, Omer.Katz, aconrad, alex, andrix, arigo, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, hozn, jcea, jhylton, jmehnle, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, ncoghlan, neologix, nirai, phsilva, pitrou, portante, rcohen, rh0dium, scoder, tarek, thouis, victorpoluceno, vstinner, ysj.ray
Date	2019年07月10日.22:49:36
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1562798976.57.0.0238995791969.issue7946@roundup.psfhosted.org>

Content
I suggest: (1) turning one of the patches (probably the last BFS one?) into a PR against the github master branch (3.9) and, (2) if none of the existing pyperformance workloads already demonstrates the problems with the existing GIL implementation, adopt one of the benchmarks here into an additional pyperformance workload. (3) demonstrate pyperformance results (overall and targeted tests) before and after the change. Simultaneously, it'd also be interesting to see someone create an alternate PR using a PyPy inspired GIL implementation as that could prove to be a lot easier to maintain. Lets make a data driven decision here. People lost interest in actually landing a fix to this issue in the past because it wasn't impacting their daily lives or applications (or if it was, they already adopted a workaround). Someone being interested enough to do the work to justify it going in is all it should take to move forward.

Content

I suggest:
 (1) turning one of the patches (probably the last BFS one?) into a PR against the github master branch (3.9) and,
 (2) if none of the existing pyperformance workloads already demonstrates the problems with the existing GIL implementation, adopt one of the benchmarks here into an additional pyperformance workload.
 (3) demonstrate pyperformance results (overall and targeted tests) before and after the change.
Simultaneously, it'd also be interesting to see someone create an alternate PR using a PyPy inspired GIL implementation as that could prove to be a lot easier to maintain.
Lets make a data driven decision here.
People lost interest in actually landing a fix to this issue in the past because it wasn't impacting their daily lives or applications (or if it was, they already adopted a workaround). Someone being interested enough to do the work to justify it going in is all it should take to move forward.

History
Date	User	Action	Args
2019年07月10日 22:49:36	gregory.p.smith	set	recipients: + gregory.p.smith, loewis, jhylton, arigo, jcea, ncoghlan, pitrou, scoder, vstinner, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, phsilva, durin42, eric.araujo, nirai, alex, andrix, konryd, brian.curtin, hozn, victorpoluceno, flox, DazWorrall, cool-RR, rh0dium, rcohen, dabeaz, mahmoudimus, portante, aconrad, ysj.ray, neologix, thouis, donaldjeo, Michele, jmehnle, Dima.Tisnek, Omer.Katz
2019年07月10日 22:49:36	gregory.p.smith	set	messageid: <1562798976.57.0.0238995791969.issue7946@roundup.psfhosted.org>
2019年07月10日 22:49:36	gregory.p.smith	link	issue7946 messages
2019年07月10日 22:49:36	gregory.p.smith	create

homepage