1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
Return-Path: <obnam-dev-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from bagpuss.pepperfish.net (bagpuss.pepperfish.net [148.251.8.16])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pieni.net (Postfix) with ESMTPS id 0E7E92020B
for <distix@pieni.net>; Sun, 24 Jul 2016 11:57:33 +0200 (CEST)
Received: from platypus.pepperfish.net (unknown [10.112.100.20])
by bagpuss.pepperfish.net (Postfix) with ESMTP id 9C2FEFC5;
Sun, 24 Jul 2016 10:57:32 +0100 (BST)
Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1bRGA8-0002O7-HB; Sun, 24 Jul 2016 10:57:32 +0100
Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1bRGA6-0002Nw-Lb
for <obnam-dev@obnam.org>; Sun, 24 Jul 2016 10:57:30 +0100
Received: from pieni.net ([95.142.166.37] ident=postfix)
by mx0.pepperfish.net with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
(Exim 4.80) (envelope-from <liw@liw.fi>) id 1bRGA4-0007b3-Hz
for obnam-dev@obnam.org; Sun, 24 Jul 2016 10:57:30 +0100
Received: from exolobe3.liw.fi (91-145-75-165.bb.dnainternet.fi
[91.145.75.165])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pieni.net (Postfix) with ESMTPSA id 51ECD2020B;
Sun, 24 Jul 2016 11:57:20 +0200 (CEST)
Received: from exolobe3 (localhost [127.0.0.1])
by exolobe3.liw.fi (Postfix) with ESMTPS id 98ABA1204A4;
Sun, 24 Jul 2016 12:57:19 +0300 (EEST)
Date: Sun, 24 Jul 2016 12:57:18 +0300
From: Lars Wirzenius <liw@liw.fi>
To: =?iso-8859-1?Q?R=E9mi?= Rampin <remirampin@gmail.com>
Message-ID: <20160724095718.GH5765@exolobe3>
References: <56E8255A.9020906@gmail.com>
<1458055902-97595-1-git-send-email-remirampin@gmail.com>
<1458055902-97595-2-git-send-email-remirampin@gmail.com>
<20160711174533.GB14034@exolobe3>
<CAMto89CeCjoBrUweQidMo0AVgy39wNq4qYU9okD-KwgdBFCZmw@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CAMto89CeCjoBrUweQidMo0AVgy39wNq4qYU9okD-KwgdBFCZmw@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
X-Spam-Score: -2.7
X-Spam-Score-int: -26
X-Spam-Bar: --
X-Scanned-By: pepperfish.net, Sun, 24 Jul 2016 10:57:30 +0100
X-Spam-Report: Content analysis details: (-2.7 points)
pts rule name description
---- ---------------------- --------------------------------------------------
-1.0 PPF_USER_AGENT_MUTT User-Agent: contains Mutt (Mutt isn't a spam
tool) -0.5 PPF_USER_AGENT User-Agent: exists
0.5 PPF_MESSAGEID_NODOTS Message-Id contains no dots after the @
0.2 PPF_REFERENCES_NODOTS References contains no dots after the @
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
X-ACL-Warn: message may be spam
X-Scan-Signature: 2e3bad3f765aaee15ae51b4de60cbfd8
Cc: obnam-dev@obnam.org
Subject: Re: [PATCH 1/2] Switch to setuptools
X-BeenThere: obnam-dev@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Obnam development discussions <obnam-dev-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-dev-obnam.org>
List-Post: <mailto:obnam-dev@obnam.org>
List-Help: <mailto:obnam-dev-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============4790262178142167993=="
Mime-version: 1.0
Sender: obnam-dev-bounces@obnam.org
Errors-To: obnam-dev-bounces@obnam.org
--===============4790262178142167993==
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature"; boundary="PMULwz+zIGJzpDN9"
Content-Disposition: inline
--PMULwz+zIGJzpDN9
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 11, 2016 at 02:10:36PM -0400, R=E9mi Rampin wrote:
> 2016-07-11 13:45 EDT, Lars Wirzenius <liw@liw.fi>:
>=20
> > On Tue, Mar 15, 2016 at 11:31:41AM -0400, Remi Rampin wrote:
> > > -from distutils.core import setup, Extension
> > > +from setuptools import setup, Extension
> >
> > Can you explain why using setuptools instead of distutils? Let's
> > assume I am quite ignorant about PyPI and pip and the various Python
> > attemmpts at build tools.
> >
>=20
> setuptools has become a standard for Python packages and if people have p=
ip
> installed, you can assume they have setuptools. In particular, setuptools
> is recommended by the Packaging User Guide [1].
Oh good, yet another build depenendy, then.
> > +os.chdir(os.path.abspath(os.path.dirname(__file__)))
> >
> > Why is this line needed?
>=20
> If running the setup.py script from another working directory (pip install
> doesn't do that, but when using -e or calling it manually it can
> happen),
I don't feel that's a thing I care to support. If we are to have that
line, then at least it needs to have a comment to explain it.
If that use case for setup.py is something that should be supported,
it should be supported by setuptools directly, not by inserting code
into every setup.py file ever written.
> Yes, all of the dependencies would have to be put there. I didn't rename
> larch yet because I didn't know what to rename it to (larch is taken [2]
> but not python-larch, ...)
I don't particularly care about the name on PyPI. It's a flat
namespace, and this is one of the problems that results from that.
However, since there's no point in putting in any of this PyPI support
into Obnam before its dependencies, I am afraid I'm going to drop this
now.
I do not like PyPI, and I do not like anything about how the Python
community distributes code. I don't want to have to deal with it, and
this thread has already exceeded my tolerance level for PyPI.
--=20
Schr=F6dinger's backup hypothesis: the condition of any backup is
undefined until a restore is attempted. -- andrewsh
--PMULwz+zIGJzpDN9
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXlJD+AAoJEGwvphbseiAx6XsP/3uabuC0JlgzOYZRpEmkjkfK
Kuwd8nYp30H+j0wxr4qf3DK6aMqOhbjNxbuUINPlNOj6q+lgkWws2VneutPp129C
ppPGLS0rbfYVgiPeprqUBdsvTDmSeAAkxHPlly/H7OE0cJs3+J/JGY0SLS49LdKz
+paiJDl3Ozrzz0Hp2mDhqXEigX0sNcaW6DOu96DXMxdARX0p92Hd29v8hdunhtuI
dPjcke8PoYvyOJFv9ndcAuMLEqLRsty1lf70lQreK+6jABCLfQ3h0tz6ulh6Z3bK
0PQUWJrps1k9m6FtQlZoYr+qlqtEUoCvfneAjUHS4gDO9aUILNrZtaprFrDJGEYr
jRb6eKLJ3/xcBa1512dcy6RyqB4RIWXAena0RB4VvE3j/x7kHgFKUkTVKwlkGibY
i/lvWiYbePlEQX7Jcofbes3YX79ko0vfe++XLJJfESDyUKrS79vcQzI2Yex/boDX
Y0gbXqLIr5PjB+MWus2ew4Hj7IZ8ZOcR5HYC4cu5HrrzQL4LMFs6adBZc1bGv9Qk
Qdec2MBgJtR6vlB7buab52zubfFEed+sw9b2IUGB3xDd3Zi27wEoz3sabDanm5GJ
QpsRLJevc7iQKj+tQTSovenvwg+SCkZbvrRk7sMFjfHxd68R4ZtVOctnPvnVWctk
hOTxqPSqsON0E+uKbNel
=sxvG
-----END PGP SIGNATURE-----
--PMULwz+zIGJzpDN9--
--===============4790262178142167993==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
obnam-dev mailing list
obnam-dev@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org
--===============4790262178142167993==--
|
