Prateek wrote:
[...]
> Mainly it revolves around dedicating one core for executing
> synchronized code and doing context switches instead of acquiring/
> releasing locks.
>
> http://www.brainwavelive.com/blog/index.php?/archives/12-Suggestion-for-removing-the-Python-Global-Interpreter-Lock.html
C
On 9/13/07, Prateek <[EMAIL PROTECTED]> wrote:
> On Sep 13, 1:36 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> > Prateek wrote:
> > > Hi,
> >
> > > Recently there was some talk on removing the GIL and even the BDFL has
> > > written a blog post on it.
> > > I was trying to come up with a scal
On Sep 13, 1:36 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Prateek wrote:
> > Hi,
>
> > Recently there was some talk on removing the GIL and even the BDFL has
> > written a blog post on it.
> > I was trying to come up with a scalable and backwards compatible
> > approach for how to do it.
Prateek wrote:
> Hi,
>
> Recently there was some talk on removing the GIL and even the BDFL has
> written a blog post on it.
> I was trying to come up with a scalable and backwards compatible
> approach for how to do it.
>
> I've put my thoughts up in a blog post - and I'd really like to hear
>
