[pypy-dev] Thinking about the GIL

Benjamin Peterson benjamin at python.org
Tue Mar 15 15:17:58 CET 2011

2011/3/15  <Ben.Young at sungard.com>:
>> -----Original Message-----
>> From: pypy-dev-bounces at codespeak.net [mailto:pypy-dev-
>> bounces at codespeak.net] On Behalf Of Benjamin Peterson
>> Sent: 14 March 2011 19:29
>> To: Timothy Baldridge
>> Cc: PyPy Dev
>> Subject: Re: [pypy-dev] Thinking about the GIL
>> 2011/3/14 Timothy Baldridge <tbaldridge at gmail.com>:
>> > They may not be thread-safe, but as far as a program goes, do we
>> > really care? If I have two threads adding items to the same list,
>> > should I really be expecting the interpreter to keep things
> straight?
>> > What's wrong with forcing the user to lock structures before editing
>> > them? This is something that Java, and C#, and C++ all require.
>> Yes, the Python interpreter should never crash because of user
>> mistakes.
> C# structures aren't thread-safe, but you can't crash the CLR by using
> them in a multithreaded manner

The primitive data structures must be thread-safe, though.


More information about the Pypy-dev mailing list