Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Amend Debian Python Proposal to Include More Python Metadata?
Date: Fri, 22 Jan 2016 18:00:04 +0100
Message-ID: <qTNe4-6HG-29@gated-at.bofh.it>
References: <qTopk-6qy-11@gated-at.bofh.it> <qTLYC-5Vz-11@gated-at.bofh.it> <qTMhZ-62g-15@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="nextPart1777971.evxMpdSXJF"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 93
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:8119


--nextPart1777971.evxMpdSXJF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Friday, January 22, 2016 10:54:54 AM Donald Stufft wrote:
> > On Jan 22, 2016, at 10:36 AM, Piotr O=C5=BCarowski <piotr@debian.or=
g> wrote:
> >=20
> > to be honest, I still don't know what you're asking for. What do yo=
u
> > want us to do? Patch 2.7's distutils?
>=20
> Essentially, ensure that setuptools not distutils is used in a setup.=
py.
> There are generally three kinds of setup.py files:
>=20
> 1) Ones that use setuptools unconditionally - These ones you just lea=
ve
> alone, they are already correct and you should already have a build d=
epends
> on python-setuptools. 2) Ones that conditionally use setuptools - The=
se
> ones you just need to satisfy whatever condition the setup.py uses to=

> enable setuptools. Typically this is just checking if setuptools is
> importable but sometimes they use environment variables or similar. 3=
) Ones
> that use distutils unconditionally - These ones you switch to making =
them
> use setuptools instead of distutils.
>=20
> Now, that=E2=80=99s the high level overview, there=E2=80=99s an easie=
r, more automatic way
> that could maybe just be added to pybuild (Not sure exactly how pybui=
ld
> works) where instead of invoking the setup.py as:
>=20
>     python setup.py install (or whatever commands/args you=E2=80=99re=
 passing)
>=20
> You do it as (taken from pip):
>=20
>     python -c "import setuptools,
> tokenize;__file__=3D'$PWD/setup.py';exec(compile(getattr(tokenize, 'o=
pen',
> open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))=E2=80=
=9D install
> (or whatever commands/args you=E2=80=99re passing).
>=20
> The thing is kind of ugly, but that will install things using setupto=
ols
> (just like pip does) regardless of if it imports setuptools or distut=
ils in
> it=E2=80=99s setup.py file.

I tried this and it works, but what's the big deal?

It provides a PKG-INFO file that has identical content to the old egg-i=
nfo file,=20
an empty dependency links file, and a top_level.txt file with the one l=
ine in=20
it.

Why is this better (I'm not a huge upstream developer of Python stuff, =
but I do=20
do some and I don't see what this gets me)?

Scott K
--nextPart1777971.evxMpdSXJF
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)

iQIcBAABCAAGBQJWol4ZAAoJEHjX3vua1ZrxlDsP/A3Y8DEl6FfcmZJPu2G/7bbp
ZUXqfbpfGLrYVaOkt0fS2PiUUUvs14EkM7tm2ghBoDJ1A/4nQOYK30vPP6odBIME
+cd2/HpUw7N23im3R/y/bAhZl64O/MkCD30qdDp/umGHdOUDw3gq3KNl9RJ3trLL
kD5YAPrWN4fv73d/+aJkvjoYJQnmDpBl56kf84D6uxF6eA2LoAzdJOwwlZ+Nu6sI
/gpzQK7FinsWJX1Y1GFKJMoxsvsPYMQz3y/WPeNnCYyIgzJRcjTlKxMps2zKALaV
QU+ys482KLQp+DkWV4P6tGu7C9LLRF1LURw9+0sXdsFt2EdljMXc2FlEgdcnnJ1h
9nsUaynuCF5hh8Aa5/lvOYx+TupGJVHnNqQsn80HV3VsRPoX9jaHh/znpRn0LalL
KHxAREQVqAmxqyqojlmi2z71l3UkIiqj4IRTjfX47LO9oU7VYF28KCDLPuOcSHEk
aFTIVKFd45fo0m8KCk0YJBCN4NwRDqjy2SlNdCd+RjmuM9x+GKXbu4Mt7wq2sN3q
h+6a49RIMHrOIhmg/lH8cBM82H3hZ9ZimNN8XREpIrYOI41RBhPiCmuHrv3kDuMU
6/rwFfS2ILIdw5Z40HSAwHAH1ZT0bGq7YHvUOUqLG6VPR1qAdMAMyzaKxYPqW2G1
jVKOP/C16gPKFLhtMZ6T
=hocE
-----END PGP SIGNATURE-----

--nextPart1777971.evxMpdSXJF--