GNU bug report logs - #24450
pypi importer outputs strange character series in optional dependency case.

Previous Next

Package: guix;

Reported by: ng0 <ng0 <at> we.make.ritual.n0.is>

Date: Fri, 16 Sep 2016 20:02:01 UTC

Severity: normal

Tags: patch

Merged with 24557, 33047, 33569, 34266

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ng0 <ng0 <at> we.make.ritual.n0.is>
Subject: bug#24450: closed (Re: bug#24450: [PATCHv3] Re: pypi importer
 outputs strange character series in optional dependency case.)
Date: Tue, 02 Jul 2019 01:55:04 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#24450: pypi importer outputs strange character series in optional dependency case.

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 24450 <at> debbugs.gnu.org.

-- 
24450: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24450
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ricardo Wurmus <ricardo.wurmus <at> mdc-berlin.de>
Cc: 24450-done <at> debbugs.gnu.org
Subject: Re: bug#24450: [PATCHv3] Re: pypi importer outputs strange character
 series in optional dependency case.
Date: Tue, 02 Jul 2019 10:54:30 +0900
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Here's the current patch set, version 3, with the modifications
> as discussed in the previous exchanges [...]

I've now merged this patch series (version 3) into master, with top
commit 4b60ab8c006964d026dee8cf5f1260eba0b2bb81.

Closing.

Thank you!

Maxim

[Message part 3 (message/rfc822, inline)]
From: ng0 <ng0 <at> we.make.ritual.n0.is>
To: bug-guix <at> gnu.org
Subject: pypi importer outputs strange character series in optional dependency
 case.
Date: Fri, 16 Sep 2016 20:00:02 +0000
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



This bug report was last modified 6 years and 18 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.