[Python-ideas] Was: Annotations (and static typing), Now:Sharing __annotations__

[Nick Coghlan]

On 24 August 2014 23:32, Cem Karan <cfkaran2 at gmail.com> wrote:
>
> - Using PyPI means that every programmer that is trying to follow the standard (including anyone who is just learning python) will create some name while practicing.  That name will need to be pushed up to PyPI to ensure uniqueness.  Since most of these names are only for learning, PyPI will immediately get flooded with a bunch of project names that are probably going to be abandoned almost immediately (I'm thinking of beginning programming classes especially).  This would significantly degrade the utility of PyPI, which I want to avoid.  All similar centrally-managed systems will suffer from the same problem.  UUIDs don't have this problem; create and abandon them at will.

If someone is just experimenting locally, it doesn't matter if they
pick a conflicting name. If they're distributing, they're going to
need to register a name on PyPI anyway.

The fact that potential conflicts only matter once people start to
consider distribution is crystal clear for distribution metadata,
which is why PyPI names are the proposed namespacing mechanism for
avoiding naming conflicts for extensions to metadata 2.0 (see the PEP
426 draft for details).

(Note I don't really like this idea in general - if it's not for
humans, then it doesn't need to be in the annotations dict, it can go
in a separate file. But the UUIDs for namespacing idea fails badly on
the "Readability counts" front)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia