From: ng0 <ng0@we.make.ritual.n0.is>
To: 24450@debbugs.gnu.org
Subject: bug#24450: pypi importer outputs strange character series in optional dependency case.
Date: Fri, 16 Sep 2016 20:00:02 +0000 [thread overview]
Message-ID: <87h99fipj1.fsf@we.make.ritual.n0.is> (raw)
I think this should not happen with pypi import:
(inputs
`(("python-certifi==2016.2.28"
,python-certifi==2016.2.28)
("python-dateutil==2.5.3"
,python-dateutil==2.5.3)
("python-flask-babel==0.11.1"
,python-flask-babel==0.11.1)
("python-flask==0.11.1" ,python-flask==0.11.1)
("python-lxml==3.6.0" ,python-lxml==3.6.0)
("python-ndg-httpsclient==0.4.1"
,python-ndg-httpsclient==0.4.1)
("python-pyasn1-modules==0.0.8"
,python-pyasn1-modules==0.0.8)
("python-pyasn1==0.1.9" ,python-pyasn1==0.1.9)
("python-pygments==2.1.3"
,python-pygments==2.1.3)
("python-pyopenssl==0.15.1"
,python-pyopenssl==0.15.1)
("python-pyyaml==3.11" ,python-pyyaml==3.11)
("python-requests[socks]==2.10.0"
,#{python-requests\x5b;socks\x5d;==2.10.0}#)
("python-setuptools" ,python-setuptools)))
I can understand the version numbers, I can also understand the optional
socks building/module of the python-requests, but why does it read like
Gobbledygook? Can't we improve the output here?
For version numbers, this is not a format which happened recently which
is exclusive for python build system right? This is just bad formated
because of the pypi query.
I will first try and not pin the application to these version numbers,
maybe itjustworks™.
To reproduce: "guix import pypi searx"
--
ng0
next reply other threads:[~2016-09-16 20:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 20:00 ng0 [this message]
2019-03-29 4:24 ` bug#24450: pypi importer outputs strange character series in optional dependency case Maxim Cournoyer
2019-06-16 17:02 ` ng0
2019-06-26 4:12 ` Maxim Cournoyer
2019-03-29 4:34 ` bug#24450: [PATCH] " Maxim Cournoyer
2019-03-30 2:12 ` bug#24450: [PATCHv2] " T460s laptop
2019-03-31 14:40 ` bug#24450: [PATCH] " Maxim Cournoyer
2019-04-01 15:28 ` bug#24450: [PATCHv2] " Ludovic Courtès
2019-05-15 11:06 ` Ricardo Wurmus
2019-05-20 4:05 ` bug#24450: [PATCHv2] " Maxim Cournoyer
2019-05-20 15:05 ` Ludovic Courtès
2019-05-22 1:13 ` Maxim Cournoyer
2019-05-27 14:48 ` Ricardo Wurmus
2019-06-10 2:10 ` Maxim Cournoyer
2019-05-27 15:11 ` Ricardo Wurmus
2019-06-10 3:30 ` Maxim Cournoyer
2019-06-10 9:23 ` Ricardo Wurmus
2019-06-16 14:11 ` Maxim Cournoyer
2019-06-17 1:41 ` Ricardo Wurmus
2019-05-27 15:54 ` Ricardo Wurmus
2019-06-10 8:32 ` Maxim Cournoyer
2019-06-10 9:12 ` Ricardo Wurmus
2019-06-16 6:05 ` Maxim Cournoyer
2019-05-27 15:58 ` Ricardo Wurmus
2019-05-28 10:23 ` Ricardo Wurmus
2019-06-10 13:30 ` Maxim Cournoyer
2019-06-10 20:13 ` Ricardo Wurmus
2019-05-28 11:04 ` Ricardo Wurmus
2019-06-11 0:39 ` Maxim Cournoyer
2019-06-11 11:56 ` Ricardo Wurmus
2019-05-28 13:21 ` Ricardo Wurmus
2019-05-28 14:48 ` Ricardo Wurmus
2019-06-16 5:10 ` Maxim Cournoyer
2019-05-28 14:53 ` Ricardo Wurmus
2019-05-30 2:24 ` Maxim Cournoyer
2019-06-16 5:53 ` Maxim Cournoyer
2019-06-12 3:00 ` Maxim Cournoyer
2019-06-12 6:39 ` Ricardo Wurmus
2019-06-16 14:29 ` Maxim Cournoyer
2019-06-16 14:36 ` bug#24450: [PATCHv3] " Maxim Cournoyer
2019-07-02 1:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h99fipj1.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=24450@debbugs.gnu.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.
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.