On Wed, Aug 10, 2011 at 10:19 AM, Brian Curtin <brian.curtin at gmail.com> wrote: > On Wed, Aug 10, 2011 at 11:14, Vlad Riscutia <riscutiavlad at gmail.com> wrote: >> >> Removing GIL is interesting work and probably multiple people are willing >> to contribute. Threading and synchronization is a deep topic and it might be >> that if just one person toys around with removing GIL he might not see >> performance improvement (not meaning to offend anyone who tried this, >> honestly) but what about forking a branch for this work, with some good >> benchmarks in place and have community contribute? Let's say first step >> would be just replacing GIL with some fine grained locks with expected >> performance degradation but afterwards we can try to incrementally improve >> on this. >> Thank you, >> Vlad > > Feel free to start this: http://hg.python.org/cpython +1 on not waiting for someone else to do it if you have an idea. :) Bitbucket makes it really easy for anyone to fork a repo into a new project and they keep an up to date mirror of the CPython repo: https://bitbucket.org/mirror/cpython/overview -eric > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/ericsnowcurrently%40gmail.com > >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4