Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'author:': 0.03; '(at': 0.04; 'booth': 0.09; 'inclusion': 0.09; 'okay': 0.09; 'subject:PyPI': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; 'project,': 0.12; 'posted': 0.15; 'ah!': 0.16; 'bsd': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'ignoring': 0.16; 'license:': 0.16; 'sad': 0.16; 'wrote:': 0.18; 'code.': 0.18; 'else,': 0.19; 'thu,': 0.19; '(in': 0.22; 'proposed': 0.22; 'separate': 0.22; 'cc:addr:python.org': 0.22; 'cc:2**0': 0.24; 'options': 0.25; 'changes,': 0.26; 'equivalent': 0.26; 'possibly': 0.26; 'somewhere': 0.26; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'forgot': 0.30; 'then.': 0.30; 'message- id:@mail.gmail.com': 0.30; 'code': 0.31; 'author,': 0.31; 'trivial': 0.31; 'there.': 0.32; 'maintaining': 0.32; 'option': 0.32; 'another': 0.32; 'minimal': 0.33; 'actual': 0.34; 'maybe': 0.34; "can't": 0.35; 'anywhere': 0.35; 'possible.': 0.35; 'case,': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'version': 0.36; 'dies': 0.36; "he's": 0.36; 'version,': 0.38; 'pm,': 0.38; 'manually': 0.60; 'most': 0.60; 'back': 0.62; 'email addr:gmail.com': 0.63; 'name': 0.63; 'him,': 0.64; 'different': 0.65; 'license': 0.66; 'contact': 0.67; 'stated': 0.69; 'touch': 0.74; 'confusion.': 0.84; 'absolutely': 0.87; 'to:none': 0.92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=UAnFxaHvqFLd0Tmd5cvYSUpAGHESPPop1OnTuv0KxME=; b=e5k7EORyns7N18YWpTO9VZ+JcPq3EgPGrNvDoF872KniycHmrc58bNAiXI+PAlm3VU mTKViQoRSilGDYupqLQDPQDHYCTkpUIN9gZk4gcUPLqhbcxlonXCZJNr4jlAogBGfFCv mRatQPV8dV2u5Ta9nutsgHPZc10aac0pCa2PIgFx2h3ZQSbUULDxCY33Jb+odzVBZUJT OD6rQWEvcZg3zCTL45R1bMQQgXq6nhTQkSiJSAQHC0WvmgpGdhCKh5be3Iu9QAsnXL7F qG4L+X5tuk/cJo3DI6rTx7WPtdrjQFiiLr47TqeQdmmZdpGn7Pe5x8/ZOK1IYUkUsVdg Ph0w== MIME-Version: 1.0 X-Received: by 10.58.85.3 with SMTP id d3mr5058390vez.34.1401350785816; Thu, 29 May 2014 01:06:25 -0700 (PDT) In-Reply-To: References: <1fgpxn70wxrg0.1rv21r79ohz7z$.dlg@40tude.net> Date: Thu, 29 May 2014 18:06:25 +1000 Subject: Re: Forking PyPI package From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 39 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1401350795 news.xs4all.nl 2918 [2001:888:2000:d::a6]:33331 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:72226 On Thu, May 29, 2014 at 5:56 PM, Duncan Booth wrote: > Chris Angelico 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