Re: [Jython-dev] RE: [Python-sets] re: status of set.py?

[Samuele P. <pe...@in...>]

> I confess I make this tradeoff in the same direction for virtually all data
> structures I implement in Python:  it's great that operations on the builtin
> types act atomic, but I usually consider it my client code's problem for
> non-thread-specific services coded in Python.  Indeed, it seems like almost
> everyone does.  Common Java practice differs (perhaps because of direct
> language support for "synchronized" methods).
> 

Java has changed philosophy too. The new (java 2) collection
classes are not thread-safe by default, you should use
appropriate synchronizing wrappers to obtain that behavior.

regards, Samuele.