From: ng0 <ng0@n0.is>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 29847@debbugs.gnu.org
Subject: [bug#29847] [PATCH] import: pypi: Stay in the REPL if fail to get a source
Date: Mon, 25 Dec 2017 19:38:25 +0000 [thread overview]
Message-ID: <20171225193825.pngvygr4gkprorap@abyayala> (raw)
In-Reply-To: <87shbyol9i.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Hi,
Oleg Pykhalov transcribed 1.6K bytes:
> Hello ng0,
>
> ng0 <ng0@n0.is> writes:
>
> > Why? Could you give some reasons why the current behavior is bad
> > and what your code tries to improve in this regard?
>
> Because of the documentation string says “return #f on failure” (not
> kill REPL on failure or terminate a Guile process):
>
> Fetch the metadata for PACKAGE-NAME from pypi.python.org, and return the
> `package' s-expression corresponding to that package, or #f on failure.
>
> and because Why an import package function kill my Emacs's Geiser? :'(
>
>
> I'm trying to implement recursive-import for pypi based on cran's
> recursive-import. Killing Guile process will be an issue, I guess.
>
> Oleg.
Okay, sounds reasonable. I just thought an explanation would be
good. Preferable we should add those to the commits more often.
Context is good :)
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-25 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 13:46 [bug#29847] [PATCH] import: pypi: Stay in the REPL if fail to get a source Oleg Pykhalov
2017-12-25 13:59 ` ng0
2017-12-25 15:55 ` Oleg Pykhalov
2017-12-25 19:38 ` ng0 [this message]
2017-12-29 11:14 ` Danny Milosavljevic
2018-01-11 21:39 ` Ludovic Courtès
2018-03-29 13:16 ` Ludovic Courtès
2018-04-01 13:26 ` Oleg Pykhalov
2018-04-02 16:16 ` bug#29847: " Ludovic Courtès
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=20171225193825.pngvygr4gkprorap@abyayala \
--to=ng0@n0.is \
--cc=29847@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/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.