From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: 20765@debbugs.gnu.org
Subject: bug#20765: Compressed eggs (Python)
Date: Wed, 06 Apr 2016 22:52:04 +0200 [thread overview]
Message-ID: <87oa9m4g0b.fsf_-_@gnu.org> (raw)
In-Reply-To: <20160406181724.GA18933@bugis> (Andreas Enge's message of "Wed, 6 Apr 2016 20:17:24 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> Spending a week with Python wizards, I asked around and got the following
> advice, implemented in the package as
> #:configure-flags '("--single-version-externally-managed" "--root=/")
Woow, I wouldn’t have guessed that this has something to do with .egg
compression. :-)
> Our Python build system adds these flags only to the install phase.
>
> We could do this automatically in our Python build system, but we would
> need to make sure to add these flags only when python-setuptools or
> python2-setuptools are part of the input, since the flags are not recognised
> by the setup.py from distutils.
OK. If the above flags do the trick, then why not. The difficulty will
be to find a nice way to determine whether those flags can be passed.
> Another advice was to replace the call to "python setup.py install"
> by "pip install .", which apparently is becoming the standard approach
> of installing Python packages, not only over the Internet, but also locally
> (for which the "." stands).
Dunno, but that’s a different story. :-)
Thanks!
Ludo’.
next prev parent reply other threads:[~2016-04-06 20:53 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
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 ` Ludovic Courtès [this message]
2016-04-18 19:21 ` bug#20765: Compressed eggs (Python) 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa9m4g0b.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=20765@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.