On Mon, Oct 31, 2011 at 1:11 PM, Mike Meyer <mwm@mired.org> wrote:
The one glaring exception is in concurrent programs. While the tools python has for dealing with such are ok, there isn't anything to warn you when you fail to use those tools and should be.
This will basically run into the same problem that free-threading-in-CPython concepts do - the fine grained checks you need to implement it will kill your single-threaded performance. Since Python is a scripting language that sees heavy single-threaded use, that's not an acceptable trade-off. Software transactional memory does offer some hope for a more reasonable alternative, but that has its own problems (mainly I/O related). It will be interesting to see how PyPy's experiments in this space pan out. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia