RetroSearch Browse

Thu Jun 28 15:49:42 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-June/120825.html

On Thu, 28 Jun 2012 12:53:47 +0200, =?ISO-8859-1?Q?Beno=EEt_Bryon?= <benoit at marmelune.net> wrote:
> Le 27/06/2012 22:08, Yury Selivanov a Ã©crit :
> > With python adoption (enterprise too) growing, we will inevitably
> > find out that one single namespace (PyPI) is not enough, and
> > name collisions will become a frequent headache.
> 
> * on Github, people work in a user space. All projects are
>    managed under the user account. Groups and companies
>    can use organization accounts. This scheme seems popular
>    and comfortable.
> 
> * on Github, people can fork projects. Project names are
>    not unique, but "user/organization+project name" is
>    unique. It seems to work well.
> 
> * sometimes, forks become more popular than original
>    projects. Sometimes original projects are abandoned
>    and several forks are active.
> 
> * Notice that distinct projects (i.e. not forks) can
>    have the same name, provided they are owned by distinct
>    users.

That is completely irrelevant.  The top level name in the github case
isolates the forks only.  It has nothing to do with the organization of
the *software*, only the *forks*.  Within the fork, the software itself
retains the same name...that's the whole point.

--David

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

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/120825.html below:

naming conventions and recipes related to packaging