From: "W. Trevor King" <wking@tremily.us>
To: Mike Gilbert <floppym@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] [PATCH] distutils-r1: Move egg-base to ${BUILD_DIR}/egg-info and prepend to PYTHONPATH
Date: Sun, 19 Oct 2014 10:36:55 -0700 [thread overview]
Message-ID: <20141019173655.GN17200@odin.tremily.us> (raw)
In-Reply-To: <1413680278-8109-1-git-send-email-floppym@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Sat, Oct 18, 2014 at 08:57:58PM -0400, Mike Gilbert wrote:
> This resolves a testing failure in dev-python/cryptography-1.6.1.
>
> cryptography.hazmat.backends._available_backends() scans the
> available setuptools entry_points, and so depends on having a valid
> egg-info/entry_points.txt file available.
This sounds like the issue fixed by my Setuptools patch [1,2]. If I
can reproduce the test failure and confirm that my Setuptools patch
fixes it, can we use my patch when building Setuptools until it lands
upstream?
Cheers,
Trevor
[1]: https://bugs.gentoo.org/show_bug.cgi?id=524322
[2]: https://bitbucket.org/pypa/setuptools/pull-request/85/egg_info-search-egg-base-for-files-to-add/diff
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-19 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 0:57 [gentoo-python] [PATCH] distutils-r1: Move egg-base to ${BUILD_DIR}/egg-info and prepend to PYTHONPATH Mike Gilbert
2014-10-19 17:36 ` W. Trevor King [this message]
2014-10-19 18:04 ` Mike Gilbert
2014-10-19 18:08 ` Mike Gilbert
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=20141019173655.GN17200@odin.tremily.us \
--to=wking@tremily.us \
--cc=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=python@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox