Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Barry Warsaw Newsgroups: linux.debian.maint.python Subject: Re: Python Policy: Things to consider for Stretch Date: Sat, 23 Jan 2016 00:00:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jan 22 22:55:39 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Organization: The Organization of Unorganized Woozalists X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.29; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/2dlkfVbiV3_Oc7W54IIk1CP"; protocol="application/pgp-signature" X-Mailing-List: archive/latest/13454 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20160122175519.5cb7542e@anarchist.wooz.org Approved: robomod@news.nic.it Lines: 81 Sender: robomod@news.nic.it X-Original-Date: Fri, 22 Jan 2016 17:55:19 -0500 X-Original-Message-ID: <20160122175519.5cb7542e@anarchist.wooz.org> X-Original-References: <1705132.RfqMtW1P2v@kitterma-e6430> Xref: csiph.com linux.debian.maint.python:8130 --Sig_/2dlkfVbiV3_Oc7W54IIk1CP Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Jan 21, 2016, at 10:47 AM, Scott Kitterman wrote: >I've taken a run through the current Python Policy to see where I think it >needs to be updated for Stretch. Thanks Scott for the badly needed update. Some comments, apologies for the lack of good quoting, or if I've read the diff incorrectly. 2.5 Module Path "Public Python modules must be installed in the system Python modules directory, /usr/lib/python./dist-packages. Public Python 3 modules m= ust be installed in /usr/lib/python3/dist-packages." I think this could use a bit of disambiguation, sice "system Python modules" could mean either Python generically, in which case the second sentence is = in conflict. Do you mean "system Python 2 modules"? If so, let's say that. Also, since Python 2.7 is all there will be from now on, why not say that explicitly? A good reason not to would be because Policy needs to cover older releases where there can be multiple versions of Python 2. But then later in your d= iff you seem to mention python2.7 as being associated with /usr/local/lib/python2./dist-packages. So maybe say /usr/local/lib/python2.7/dist-packages here too? There really won't be any other value for than 7. 3.4 Specifying Supported Versions "The optional `X-Python-Version (preferred) or `XS-Python-Version` field..." It's a little confusing because we're now saying we prefer not to have eith= er field. How about "(previously preferred)" or just drop the parenthetical? 3.6 Provides s/substituation/substitution/ B.2. dh_python2 and dh_python3 Again, I think here you want to say "Python2 and Python3" to disambiguate between generic Python. Other than that, +1 Cheers, -Barry --Sig_/2dlkfVbiV3_Oc7W54IIk1CP Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWorNXAAoJEBJutWOnSwa/lMwQAKpbvtjRItVHZan/H2NlYkKk PrQx5jbAfmAADo02EGebv7wC5Fau9qDg72uuVg9FIt08qGzYBzpUtk9Uistbt6MC 7qP7hcAnNREkJbat7tIEx39Jlf8ZIkrq4XobgCPtHhGqW6W6+MJfTeOmqOpUC3HY 035U3GpTuQtM/nIjpemyJ3JoG3LjldkTQTCjWoTxUCr2jXTqJNMGSKMliWYCFiii DDltGeZD7cH6YnLDZ2M/d9bQ7GZZLa/37o6L7WteDapkambDsudoa8X3PPIpUOFZ uVZoqXEgya6k7mSvt/r3T7yFL6fq9qrqH6+hw1JdG6BBYBex6OMUUIjTGQpMiXdt qHTKcdV7Bq//2wZFF4b8o+h3FW1EKcdB2lks+uvah2WWXcqgUOFaJB1EFsAfvtqe ti872KjWWnAiohPlMS0RETNSxAeXOSvg+1sphR9S3Lm2GMQX79x0CYss+JFSDa50 94920bQczmFCgMhNjy4B5TUn5BqfNElzNrDs5QgsdAC5TmkkVl2dBHVM/A4NbWGE CBs650wlxPTEaPfR0N6x8fuctLxLWKC0oukI58v0rFn9yCFGN0qoueYmr7PUcDDH r6vs3s4X4gx6VLMwgRSkb8G2vLfo9uulOHhO3f4Y6YJY/IGldwfZtsh5XPoIz/ak jCbp1YSiNamJyg00bRVF =y0Ba -----END PGP SIGNATURE----- --Sig_/2dlkfVbiV3_Oc7W54IIk1CP--