From: Ricardo Wurmus <rekado@elephly.net>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: 47746@debbugs.gnu.org
Subject: bug#47746: pypi importer generates wrong pypi-uri without underscore
Date: Tue, 13 Apr 2021 23:39:32 +0200 [thread overview]
Message-ID: <87h7k9uanf.fsf@elephly.net> (raw)
In-Reply-To: <87y2dmf20v.fsf@yoctocell.xyz>
Xinglu Chen <public@yoctocell.xyz> writes:
> On Tue, Apr 13 2021, Ricardo Wurmus wrote:
>
>> When importing a package from Pypi whose name includes an
>> underscore, the importer will generate a pypi-uri expression
>> where
>> the underscore has been replaced with a dash.
>
> Hmm, I just grabbed a random package from PyPi, and the URI
> seems fine
> to me. […]
> How would I reproduce the bug?
You’re right, this only affects some packages. Here are two
examples:
--8<---------------cut here---------------start------------->8---
./pre-inst-env guix import pypi -r jupyterlab_widgets
following redirection to
`https://pypi.org/pypi/jupyterlab-widgets/json'...
[…] (uri (pypi-uri "jupyterlab-widgets" version)) […]
--8<---------------cut here---------------end--------------->8---
--8<---------------cut here---------------start------------->8---
./pre-inst-env guix import pypi -r jupyter_packaging
following redirection to
`https://pypi.org/pypi/jupyter-packaging/json'...
[…] (uri (pypi-uri "jupyter-packaging" version)) […]
--8<---------------cut here---------------end--------------->8---
They both have a redirection in common, but the pypi-uri is
incorrect as it needs to have the underscore.
--
Ricardo
next prev parent reply other threads:[~2021-04-13 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 8:17 bug#47746: pypi importer generates wrong pypi-uri without underscore Ricardo Wurmus
2021-04-13 18:54 ` Xinglu Chen
2021-04-13 21:39 ` Ricardo Wurmus [this message]
2021-04-14 12:45 ` Xinglu Chen
2021-04-19 2:37 ` Maxim Cournoyer
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=87h7k9uanf.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=47746@debbugs.gnu.org \
--cc=public@yoctocell.xyz \
/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).