Path: csiph.com!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: Sun, 24 Jan 2016 07:10:01 +0100
Message-ID: <qUm25-DV-3@gated-at.bofh.it>
References: <qTpEL-7eF-19@gated-at.bofh.it> <qUlIJ-fU-3@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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Approved: robomod@news.nic.it
Lines: 77
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:8149

On Sunday, January 24, 2016 04:46:09 PM Ben Finney wrote:
> Scott Kitterman <debian@kitterman.com> writes:
> > I've taken a run through the current Python Policy to see where I
> > think it needs to be updated for Stretch. The updates largely fall
> > into four categories: [=E2=80=A6]
>=20
> This is great to see, thank you Scott.
>=20
> Where is the Git (I assume?) repository you're using for VCS of this
> policy document?

It's in bzr, actually.  You can find the repository at=20
https://alioth.debian.org/scm/loggerhead/pkg-python/python-defaults-deb=
ian/files (that page has a link to make a branch using bzr.

The Python Policy is in debian/python-policy.sgml

You can make a text version using:

debiandoc2text debian/python-policy.sgml

> > This is just my opinion on stuff I found. I'm interested in feedbac=
k
> > on how these changes look and what else ought to be considered
>=20
> I like what I see (modulo other discussions in this thread).
>=20
>=20
> One small nit: the examples of what is included versus excluded of th=
e
> =E2=80=9Cscope=E2=80=9D of a Python version reference. It used to say=
:
>=20
>      as it seems reasonable to provide them.  (Note: For the scope of=
 this
>      document, Python versions are synonymous to feature releases, i.=
e.
>      Python 2.7 and 2.7.1 are sub-minor versions of the same Python v=
ersion
>      2.7, but Python 2.6 and 2.7 are indeed different versions.)
>=20
> The contrast =E2=80=9C2.7 and 2.7.1 are [=E2=80=A6] the same Python v=
ersion 2.7=E2=80=9D, with
> =E2=80=9C2.6 and 2.7 are [=E2=80=A6] different versions=E2=80=9D, use=
s version =E2=80=9C2.7=E2=80=9D in both
> parts.
>=20
> I think it's important to the example that an *identical* version is =
in
> *both* arms of that contrast, to be clear what is being distinguished=
.
>=20
> So in the re-write I'd advise again using an identical version in bot=
h
> parts:
>=20
>      as it seems reasonable to provide them.  (Note: For the scope of=
 this
>      document, Python versions are synonymous to feature releases, i.=
e.
>      Python 3.5 and 3.5.1 are sub-minor versions of the same Python v=
ersion
>      3.5, but Python 3.4 and 3.5 are indeed different versions.)
>=20
> If I can know where to access the VCS repository I can make a patch f=
or
> that, if you like.

Great.  See above.

I just pushed the edits I've proposed so what's in there now should be =
clean=20
for you to work on top of.  Pushing them to the repository doesn't make=
 them=20
any less draft in my opinion (in case anyone was wondering).

Scott K