From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] distutils-r1.eclass: Namespace & doc _clean_egg_info
Date: Tue, 16 May 2017 19:19:32 +0200 [thread overview]
Message-ID: <1494955172.1591.5.camel@gentoo.org> (raw)
In-Reply-To: <20170505212845.18868-1-mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
On pią, 2017-05-05 at 23:28 +0200, Michał Górny wrote:
> Prefix the _clean_egg_info function with an appropriate namespace,
> and document its purpose with eclassdoc format. Be more verbose
> on the exact problem being solved; remove URL to old upstream bug
> tracker that no longer exists.
> ---
> eclass/distutils-r1.eclass | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> ** REVIEW NOTE **
>
> Do we still need this hack? Is there any chance the issue has been
> fixed upstream? Can someone test it and find a bug upstream and/or
> re-report it?
>
> diff --git a/eclass/distutils-r1.eclass b/eclass/distutils-r1.eclass
> index 5df7234332d3..1376326c9579 100644
> --- a/eclass/distutils-r1.eclass
> +++ b/eclass/distutils-r1.eclass
> @@ -770,10 +770,14 @@ distutils-r1_src_compile() {
> fi
> }
>
> -_clean_egg_info() {
> - # Work around for setuptools test behavior (bug 534058).
> - # https://bitbucket.org/pypa/setuptools/issue/292
> - rm -rf "${BUILD_DIR}"/lib/*.egg-info
> +# @FUNCTION: _distutils-r1_clean_egg_info
> +# @INTERNAL
> +# @DESCRIPTION:
> +# Clean up potential stray egg-info files left by setuptools test phase.
> +# Those files ended up being unversioned, and caused issues:
> +# https://bugs.gentoo.org/534058
> +_distutils-r1_clean_egg_info() {
> + rm -rf "${BUILD_DIR}"/lib/*.egg-info || die
> }
>
> distutils-r1_src_test() {
> @@ -781,7 +785,7 @@ distutils-r1_src_test() {
>
> if declare -f python_test >/dev/null; then
> _distutils-r1_run_foreach_impl python_test
> - _distutils-r1_run_foreach_impl _clean_egg_info
> + _distutils-r1_run_foreach_impl _distutils-r1_clean_egg_info
> fi
>
> if declare -f python_test_all >/dev/null; then
Committed.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
prev parent reply other threads:[~2017-05-16 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 21:28 [gentoo-dev] [PATCH] distutils-r1.eclass: Namespace & doc _clean_egg_info Michał Górny
2017-05-16 17:19 ` Michał Górny [this message]
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=1494955172.1591.5.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.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