Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next v2 1/7] package/python-idna: set _SETUP_TYPE = flit
Date: Tue, 7 Feb 2023 14:31:16 +0100	[thread overview]
Message-ID: <20230207143116.40b1f42b@windsurf> (raw)
In-Reply-To: <20221122203130.184496-1-ju.o@free.fr>

On Tue, 22 Nov 2022 21:31:24 +0100
Julien Olivain <ju.o@free.fr> wrote:

> Python idna package switched to pyproject.toml in commit:
> https://github.com/kjd/idna/commit/2a00e518efe55d2eeb62cd3f88ace7db41338603
> which is included in idna v3.4.
> 
> When using the old setuptools infra, the package is incorrectly
> installed as v0.0, which is then incorrectly detected by other
> packages when using setuptools pkg_resources.
> 
> The issue can be reproduced with the command:
> 
>     python3 <<EOF
>     __requires__ = ["idna >= 2.5"]
>     import pkg_resources
>     EOF
> 
> which will fail with output:
> 
>     pkg_resources.ContextualVersionConflict: (idna 0.0.0 (/usr/lib/python3.11/site-packages), Requirement.parse('idna>=2.5'), {'hyperlink'})
>     pkg_resources.DistributionNotFound: The 'idna>=2.5' distribution was not found and is required by hyperlink
> 
> This commit changes _SETUP_TYPE to "flit" to fix this issue.
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Changes v1 -> v2:
> - Included James' review comment:
>   - _SETUP_TYPE changed from pep517 to flit
> ---
>  package/python-idna/python-idna.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, entire series applied! There was really not much to fix. In one
commit, the runtime test file was forgotten in DEVELOPERS, and in
another, I've added a reference to the upstream commit for the
open(..., "rU") thing.

Thanks a lot for having added relevant runtime tests for all of this,
this is really good!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-02-07 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 20:31 [Buildroot] [PATCH next v2 1/7] package/python-idna: set _SETUP_TYPE = flit Julien Olivain
2022-11-22 20:31 ` [Buildroot] [PATCH next v2 2/7] package/python-hkdf: new package Julien Olivain
2022-11-22 20:31 ` [Buildroot] [PATCH next v2 3/7] package/python-spake2: " Julien Olivain
2022-11-22 20:31 ` [Buildroot] [PATCH next v2 4/7] package/python-magic-wormhole: " Julien Olivain
2022-11-22 20:31 ` [Buildroot] [PATCH next v2 5/7] package/python-magic-wormhole-mailbox-server: " Julien Olivain
2022-11-22 20:31 ` [Buildroot] [PATCH next v2 6/7] package/python-magic-wormhole-transit-relay: " Julien Olivain
2022-11-22 20:31 ` [Buildroot] [PATCH next v2 7/7] support/testing/tests/package/test_python_magic_wormhole.py: new runtime test Julien Olivain
2022-12-21 22:21 ` [Buildroot] [PATCH next v2 1/7] package/python-idna: set _SETUP_TYPE = flit Marcus Hoffmann via buildroot
2023-02-23 19:02   ` Peter Korsgaard
2023-02-07 13:31 ` Thomas Petazzoni via buildroot [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=20230207143116.40b1f42b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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