Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #72226

Re: Forking PyPI package

References <1fgpxn70wxrg0.1rv21r79ohz7z$.dlg@40tude.net> <mailman.10441.1401349221.18130.python-list@python.org> <XnsA33C5AE7AF7ACduncanbooth@127.0.0.1>
Date 2014-05-29 18:06 +1000
Subject Re: Forking PyPI package
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.10443.1401350795.18130.python-list@python.org> (permalink)

Show all headers | View raw


On Thu, May 29, 2014 at 5:56 PM, Duncan Booth
<duncan.booth@invalid.invalid> wrote:
> Chris Angelico <rosuav@gmail.com> wrote:
>
>> If you absolutely can't get in touch with him, the only option is to
>> go back to the original protocol and manually reimplement it,
>> completely ignoring this code. It's sad but true; some code dies
>> because of a trivial thing like "Oops, I forgot to actually say that
>> this is MIT-licensed".
>>
>> (At least, I can't see a license anywhere on github there. If you can
>> find another copy of the same code somewhere else, posted by its
>> author, and including a license, then your job is easier.)
>
> Deep in the code (pwdhash / pwdhash.py.egg-info / PKG-INFO):
>
>   Author: Lev Shamardin
>   Author-email: shamardin@gmail.com
>   License: BSD
>
> Still better to get in touch with the author, but he has actually stated
> the license albeit in the most minimal way possible.

Ah! There you go then. Excellent.

In that case, the options I see are (in priority order):

1) Contact the author with your proposed changes, possibly with the
actual code or possibly leaving that for later, for inclusion in the
original project.

2) Ask the author if he's okay with you maintaining the Python 3
equivalent version as a separate project, under the same name.

3) If you can't get in touch with the author, just maintain that Py3
version, but maybe under a different name to avoid accidental
confusion.

ChrisA

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Forking PyPI package Wiktor <look@signature.invalid> - 2014-05-29 02:31 +0200
  Re: Forking PyPI package Terry Reedy <tjreedy@udel.edu> - 2014-05-28 22:06 -0400
  Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-05-29 17:40 +1000
    Re: Forking PyPI package Duncan Booth <duncan.booth@invalid.invalid> - 2014-05-29 07:56 +0000
      Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-05-29 18:06 +1000
  Re: Forking PyPI package Wiktor <look@signature.invalid> - 2014-05-29 10:49 +0200
  Re: Forking PyPI package Ian Kelly <ian.g.kelly@gmail.com> - 2014-05-29 15:54 -0600
    Re: Forking PyPI package Wiktor <look@signature.invalid> - 2014-06-05 18:56 +0200
      Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-06-06 03:37 +1000
        Re: Forking PyPI package Wiktor <look@signature.invalid> - 2014-06-06 02:15 +0200
          Re: Forking PyPI package Akira Li <4kir4.1i@gmail.com> - 2014-06-06 15:26 +0400
  Re: Forking PyPI package Chris Angelico <rosuav@gmail.com> - 2014-05-30 10:26 +1000

csiph-web