Path: csiph.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Python Policy: Things to consider for Stretch
Date: Sat, 23 Jan 2016 09:40:01 +0100
Message-ID: <qU1TH-8vM-1@gated-at.bofh.it>
References: <qTpEL-7eF-19@gated-at.bofh.it> <qTSQp-28S-1@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
User-Agent: KMail/4.13.3 (Linux/3.13.0-71-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1564534.0M0Xh2XQjE"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 99
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:8141


--nextPart1564534.0M0Xh2XQjE
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Friday, January 22, 2016 05:55:19 PM Barry Warsaw wrote:
> 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<X>.<Y>/dist-packages.  Public Python 3 modules
> must 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?

Personally I seriously dislike the trend to call Python Python 2 (and I still 
thing approving a pep to invent /usr/bin/python2 because Arch went insane was 
a horrible idea).  There's an earlier spot in the document where it says that 
everything refers to python and python3 unless it's explicit.  I'll make this 
spot /usr/lib/python2.7/dist-packages and any risk of ambiguity is, I think, 
resolved.

> 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
> diff you seem to mention python2.7 as being associated with
> /usr/local/lib/python2.<Y>/dist-packages.  So maybe say
> /usr/local/lib/python2.7/dist-packages here too?  There really won't be any
> other value for <Y> than 7.

We only need (I think) to cover packages being developed for the release the 
policy is for.  Squeeze was the last multi-python version release, so I think 
we're safe to remove python2.<Y> where way may not always be 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
> either field.  How about "(previously preferred)" or just drop the
> parenthetical?

Makes sense.  I'll do that.

> 3.6 Provides
> 
> s/substituation/substitution/

Thanks.

> B.2. dh_python2 and dh_python3
> 
> Again, I think here you want to say "Python2 and Python3" to disambiguate
> between generic Python.

If I say Python and Python3, what version can the one that's not Python3 
possibly be?  I don't think it's any less confusing than starting to call what 
we've always called "Python" "Python 2".

> Other than that, +1

Thanks for reviewing.

Scott K
--nextPart1564534.0M0Xh2XQjE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABCAAGBQJWozwKAAoJEHjX3vua1ZrxKuoQAIaGexZiTPzGz/Knm91Ndzg5
lOZ7zbSaQDQAbfrRCjRwZVo7m2002opPrn/Y7OQoaUr9pMcV9gqrdqDYmp3wBxGA
3GMzJ4W8o6ZAg6+GQe0imhn5W4WkYW5jjFn5d9XqfLtJerj1iRe/PZQdOz5Qty6B
DJscSriDewJE6TQwXDnZeP530dyDBFbRiqxUpky55ziB44ChJjpjkRlEbEACjV/I
A/lj1KoTLpybAf5Vhpn2dwHmSmxyJiz9AvS1uvWy0JXBAb0I5HFQCdqMhFDc6mm0
KQvJ/ZPjmAheWo8VgRvxEM+hBekSo2fPAhf/PKKxT+40D0pA6iLsyUKUiBcOLt3n
BqD+NCxf8QOvSBw9TctSd1pU5LIQ2l5e+NQWwMD5H6/hqKPNyc4HFYJ+W0uelXHw
2nPNVoAD1v4N3NplS3vIeS1XH4d9pES7pb2dD5TBcD5oLVWiuEdbVdTdTdB01x+h
YzES6EJbOZWcN9QzKv8U3s2GxhgHI9d1cfP6dJqLo3XwbwsMr3Y06meBMjlZ2Nq3
2YWZtE/KSs3bx+K9yVqqdnmXB2+HzIo7I8M/QQ5dAuehnsAJ3+rUfzK1vXvUCFe4
+UBpkxSai3J60uK4ytav+BkVOBPN+/GXs+1/dy9699MfPMupO5SZUu+3iR4wICjR
OVeA7UYSHAp3XWty3Kfw
=GNGa
-----END PGP SIGNATURE-----

--nextPart1564534.0M0Xh2XQjE--