From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>, 49168@debbugs.gnu.org
Subject: bug#49168: ‘guix import pypi’ misses package dependencies
Date: Tue, 22 Jun 2021 15:01:13 -0400 [thread overview]
Message-ID: <875yy53erq.fsf@gmail.com> (raw)
In-Reply-To: <ab46529b6773ef0a1b73504470be29a757a3dc3a.camel@student.tugraz.at> (Leo Prikler's message of "Tue, 22 Jun 2021 14:37:55 +0200")
Hello,
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> Am Dienstag, den 22.06.2021, 14:33 +0200 schrieb Ludovic Courtès:
>> Hi,
>>
>> Leo Prikler <leo.prikler@student.tugraz.at> skribis:
>>
>> > > Here, some of tablib’s dependencies are missing; the same problem
>> > > seems
>> > > to happen with python-django-import-export itself.
>> > >
>> > > Are we failing to parse some of the PyPI metadata?
>> > I don't think so, rather it appears as though the requires.txt is
>> > somehow malformed or ill-suited for importing. It basically marks
>> > all
>> > inputs as optional.
>>
>> Oh. So that’s first and foremost a bug of the PyPI package, right?
Sounds like so, if the inputs are required but marked as optional.
>> > Perhaps we could instruct the importer to emit comments for
>> > optional
>> > inputs like so
>> > ;; Optional inputs by section
>> > ;; -- [SECTION]
>> > ;; ("python-some-package" ,python-some-package)
>> > ;; ("python-some-other-package" ,python-some-other-package)
>> > Maybe add a command line switch to toggle these comments or a way
>> > of
>> > assuming some section, e.g. [cli] to be the thing we want to build
>> > for
>> > a package.
>>
>> A CLI switch to include optional dependencies would be nice.
+1.
>> As for emitting comments, the (not-so-) pretty printer written for
>> ‘guix
>> style’¹ could come in handy for importers and more generally in any
>> place where we need to emit comments.
> Indeed, I wasn't thinking about that when I wrote this reply, but I see
> what you mean. Should we strive to have such a pretty-printer in Guile
> as well or do we keep it to ourselves for now? :)
This sounds good too, although I haven't read about that new fancy
printer yet.
Maxim
next prev parent reply other threads:[~2021-06-22 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:20 bug#49168: ‘guix import pypi’ misses package dependencies Ludovic Courtès
2021-06-22 8:34 ` Leo Prikler
2021-06-22 12:33 ` Ludovic Courtès
2021-06-22 12:37 ` Leo Prikler
2021-06-22 19:01 ` Maxim Cournoyer [this message]
2021-06-23 13:20 ` Ludovic Courtès
2021-06-23 14:17 ` Leo Prikler
2021-06-24 9:57 ` Ludovic Courtès
2021-06-24 19:04 ` Maxim Cournoyer
2021-06-25 14:51 ` Ludovic Courtès
2021-06-25 15:25 ` Leo Prikler
2021-06-25 16:39 ` Maxim Cournoyer
2021-06-28 9:39 ` Ludovic Courtès
2022-03-08 9:28 ` zimoun
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=875yy53erq.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=49168@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=ludovic.courtes@inria.fr \
/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).