Comments on: Saturday @ Pycon http://jessenoller.com/2008/03/16/saturday-pycon/ python, programming and other things Mon, 02 Jan 2012 09:21:00 +0000 hourly 1 By: jnoller http://jessenoller.com/2008/03/16/saturday-pycon/comment-page-1/#comment-139336 jnoller Mon, 17 Mar 2008 01:36:35 +0000 http://jessenoller.com/2008/03/16/saturday-pycon/#comment-139336 With any luck, the free threading work will be incorporated into python core and enabled via a --with-freethreading flag. This means you would have 2 interpreters: A normal one, and the new one. The one catch would be that many C libraries would not work out of the box. With any luck, the free threading work will be incorporated into python core and enabled via a –with-freethreading flag. This means you would have 2 interpreters: A normal one, and the new one. The one catch would be that many C libraries would not work out of the box.

]]> By: Joseph Lisee http://jessenoller.com/2008/03/16/saturday-pycon/comment-page-1/#comment-139335 Joseph Lisee Mon, 17 Mar 2008 00:48:18 +0000 http://jessenoller.com/2008/03/16/saturday-pycon/#comment-139335 Let me reinforce the opinion that its wrong to just outright dismiss the single process multiple threads area of concurrency. My current project (<a href="http://ram.umd.edu" rel="nofollow">http://ram.umd.edu</a>) could use a lot more python code if I was able guarantee true concurrency. So I am very excited to see that there are people working on a solution to the to GIL. <br><br>Has there been any words on whether "freethreading" will be incorporated into the Python core, or is it destined to become and alternate interpreter like stackless? Let me reinforce the opinion that its wrong to just outright dismiss the single process multiple threads area of concurrency. My current project (http://ram.umd.edu) could use a lot more python code if I was able guarantee true concurrency. So I am very excited to see that there are people working on a solution to the to GIL.

Has there been any words on whether “freethreading” will be incorporated into the Python core, or is it destined to become and alternate interpreter like stackless?

]]> By: jnoller http://jessenoller.com/2008/03/16/saturday-pycon/comment-page-1/#comment-62132 jnoller Sun, 16 Mar 2008 21:36:35 +0000 http://jessenoller.com/2008/03/16/saturday-pycon/#comment-62132 With any luck, the free threading work will be incorporated into python core and enabled via a --with-freethreading flag. This means you would have 2 interpreters: A normal one, and the new one. The one catch would be that many C libraries would not work out of the box. With any luck, the free threading work will be incorporated into python core and enabled via a –with-freethreading flag. This means you would have 2 interpreters: A normal one, and the new one. The one catch would be that many C libraries would not work out of the box.

]]> By: Joseph Lisee http://jessenoller.com/2008/03/16/saturday-pycon/comment-page-1/#comment-62131 Joseph Lisee Sun, 16 Mar 2008 20:48:18 +0000 http://jessenoller.com/2008/03/16/saturday-pycon/#comment-62131 Let me reinforce the opinion that its wrong to just outright dismiss the single process multiple threads area of concurrency. My current project (<a href="http://ram.umd.edu" rel="nofollow">http://ram.umd.edu</a>) could use a lot more python code if I was able guarantee true concurrency. So I am very excited to see that there are people working on a solution to the to GIL. <br><br>Has there been any words on whether "freethreading" will be incorporated into the Python core, or is it destined to become and alternate interpreter like stackless? Let me reinforce the opinion that its wrong to just outright dismiss the single process multiple threads area of concurrency. My current project (http://ram.umd.edu) could use a lot more python code if I was able guarantee true concurrency. So I am very excited to see that there are people working on a solution to the to GIL.

Has there been any words on whether “freethreading” will be incorporated into the Python core, or is it destined to become and alternate interpreter like stackless?

]]>