From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 20765@debbugs.gnu.org
Subject: bug#20765: Python .egg files must not be compressed
Date: Tue, 13 Oct 2015 16:32:19 +0200 [thread overview]
Message-ID: <idjk2qqzvnw.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87612aq2pl.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
>> I could only coerce the build system to install plain files by adding a
>> build phase like this:
>>
>> (add-after 'unpack 'prevent-generation-of-egg-archive
>> (lambda _
>> (substitute* "setup.py"
>> (("from setuptools import setup")
>> "from distutils.core import setup"))
>> #t))
>>
>> It turns out that when ‘setuptools.setup’ is used egg archives are
>> built, when ‘distutils.core.setup’ is used, however, this does not
>> happen.
>
> But are distutils.core and setuptools the same thing? Replacing one by
> the other sounds a bit scary, no?
I’m not familiar with Python packaging. From what I understand,
distutils has much fewer features than setuptools; but in the few cases
that I tried replacing it did work out just fine.
> Still it would be nice to have a generic solution. Maybe we should
> patch setuptools itself to change its defaults?
This would probably be best, but I don’t understand setuptools enough to
propose a patch.
~~ Ricardo
next prev parent reply other threads:[~2015-10-13 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 20:37 bug#20765: Python .egg files must not be compressed Ludovic Courtès
2015-07-20 21:22 ` Ludovic Courtès
2015-10-13 13:38 ` Ricardo Wurmus
2015-10-13 14:10 ` Ludovic Courtès
2015-10-13 14:32 ` Ricardo Wurmus [this message]
2016-02-09 4:54 ` bug#20765: (no subject) Leo Famulari
2016-02-09 21:37 ` Ludovic Courtès
2016-04-06 18:17 ` Andreas Enge
2016-04-06 20:52 ` bug#20765: Compressed eggs (Python) Ludovic Courtès
2016-04-18 19:21 ` Hartmut Goebel
2016-12-17 18:43 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=idjk2qqzvnw.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=20765@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).