A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-January/051371.html below:

Moving towards Python 3.0 (was Re: [Python-Dev] Speed up functioncalls)

Moving towards Python 3.0 (was Re: [Python-Dev] Speed up functioncalls) Moving towards Python 3.0 (was Re: [Python-Dev] Speed up functioncalls)Skip Montanaro skip at pobox.com
Mon Jan 31 18:02:27 CET 2005
    Michael> CPython CAN leverage such environments, and it IS used that
    Michael> way.  However, this requires using multiple Python processes
    Michael> and inter-process communication of some sort (there are lots of
    Michael> choices, take your pick).  It's a technique which is more
    Michael> trouble for the programmer, but in my experience usually has
    Michael> less likelihood of containing subtle parallel processing
    Michael> bugs.

In my experience, when people suggest that "threads are easier than ipc", it
means that their code is sprinkled with "subtle parallel processing bugs".

    Michael> Perhaps the REAL solution is just a really good IPC library
    Michael> that makes it easier to write programs that launch "threads" as
    Michael> separate processes and communicate with them. 

Tuple space, anyone?

Skip
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4