From: "Ludovic Courtès" <ludo@gnu.org>
To: swedebugia <swedebugia@riseup.net>
Cc: 33436@debbugs.gnu.org
Subject: [bug#33436] [PATCH] gnu: Add python-warcio.
Date: Fri, 11 Jan 2019 09:29:14 +0100 [thread overview]
Message-ID: <87zhs78un9.fsf@gnu.org> (raw)
In-Reply-To: <87in0qu3xp.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 21 Nov 2018 11:21:06 +0100")
Ping!
ludo@gnu.org (Ludovic Courtès) skribis:
> Hello!
>
> swedebugia <swedebugia@riseup.net> skribis:
>
>>>>From 537b2b111a464956bdec640ea5f84c4598ea66f9 Mon Sep 17 00:00:00 2001
>> From: swedebugia <swedebugia@riseup.net>
>> Date: Mon, 19 Nov 2018 21:37:46 +0100
>> Subject: [PATCH] gnu: Add python-warcio.
>>
>> * gnu/packages/python.scm: New variable.
> ^
> Nitpick: You forgot the variable name here. :-)
>
>> + (arguments
>> + ;; FIXME: Some tests require network access. 150 out of 1354 fail
>> + '(#:tests? #f))
>
> Could you investigate a bit further? What do the test logs show?
>
> It would be good to see if these tests can be easily fixed, if they
> should definitely be skipped (for instance because they rely on some
> external service), or if it’s something else.
>
>> + (home-page "https://github.com/webrecorder/warcio")
>> + (synopsis "Streaming web archival archive (WARC) library")
>> + (description
>> + "warcio is designed for fast, low-level access to web archival
> ^^
> What about: “warcio is a Python library to read and write the WARC format
> commonly used in Web archives. It is designed for…”?
>
> Thank you,
> Ludo’.
next prev parent reply other threads:[~2019-01-11 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 20:41 [bug#33436] [PATCH] gnu: Add python-warcio swedebugia
2018-11-21 10:21 ` Ludovic Courtès
2019-01-11 8:29 ` Ludovic Courtès [this message]
2019-02-24 2:01 ` swedebugia
2019-03-04 13:43 ` Ludovic Courtès
2021-07-13 15:23 ` bug#33436: " 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=87zhs78un9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33436@debbugs.gnu.org \
--cc=swedebugia@riseup.net \
/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.