[Python-ideas] Module name [was Re: Pre-PEP: adding a statistics module to Python]

M.-A. Lemburg mal at egenix.com
Tue Aug 6 15:46:00 CEST 2013


On 06.08.2013 15:26, Antoine Pitrou wrote:
> Le Tue, 6 Aug 2013 15:42:39 +1000,
> Nick Coghlan <ncoghlan at gmail.com> a
> écrit :
>>
>> The main reason we've switched to nesting things inside other
>> namespaces is when a name is somewhat ambiguous on its own, or risks a
>> name clash with a PyPI project.
>>
>> concurrent.futures is so named to help avoid confusion with the
>> finance industry notion of "futures"
> 
> Which is completely silly. Polysemy is a fact of life in any natural
> language and disambiguation is done through context, not by being
> extremely wordy like a Java programmer.

While context works in natural languages (and computers have a
hard time understanding it :-)), it doesn't work for the Python
import mechanism, so I don't follow you.

Python has grown a lot since the days most of the stdlib
modules/packages were added, so we have to pay more attention
to name clashes.

"math.statistics" looks like a decent name, IMO.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Aug 06 2013)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/


More information about the Python-ideas mailing list