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/2008-June/079947.html below:

[Python-Dev] PEP 371 Discussion (pyProcessing Module)

[Python-Dev] PEP 371 Discussion (pyProcessing Module) [Python-Dev] PEP 371 Discussion (pyProcessing Module)r.m.oudkerk r.m.oudkerk at googlemail.com
Sun Jun 1 00:31:27 CEST 2008
On 31/05/2008, Paul Moore <p.f.moore at gmail.com> wrote:
> 2008/5/30 Farshid Lashkari <flashk at gmail.com>:
>> I'm not sure if there will be any side affects to modifying
>> sys.executable though. Should this be the official way of supporting
>> embedded interpreters or should there be a
>> multiprocessing.setExecutable() method?
>
> +1 for setExecutable (I'd prefer set_executable, to be PEP 8
> compliant). Make it explicit, rather than fiddling with stuff in sys
> manually.

That is easy to do.

An issue not mentioned in the PEP is naming conventions.  In recent
versions I have tried to consistently use mixedCase for functions and
methods (other than factory functions) because that is what threading
does (give or take settrace(), setprofile(), stack_size().)

I am certainly open to using lowercase/lower_case_with_underscores for
all functions/methods except for Process's methods and possibly
currentProcess(), but I would like some feed back on that.
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