unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Antero Mejr <antero@mailbox.org>, 56186@debbugs.gnu.org
Subject: [bug#56186] [PATCH] gnu: Add python-deepdish.
Date: Sat, 30 Jul 2022 22:54:01 +0200	[thread overview]
Message-ID: <ffd8e30e-d3ab-84e8-2711-fb51a76a8a92@telenet.be> (raw)
In-Reply-To: <20220624125033.5605-1-antero@mailbox.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 814 bytes --]

On 24-06-2022 14:50, Antero Mejr via Guix-patches via wrote:

> +                        (add-after 'unpack 'dont-vendor-six
> +                          (lambda _
> +                            (delete-file "deepdish/six.py")
> +                            (substitute* "deepdish/io/hdf5io.py"
> +                              (("from deepdish import six") "import six"))
> +                            (substitute* "deepdish/io/ls.py"
> +                              (("from deepdish import io, six, __version__")
> +                               "from deepdish import io, __version__

If you move it to an origin snippet, then the result of "guix build 
--source" becomes 'cleaner' in the sense that it actually corresponds to 
what is built, could it be moved there?

Greetings,
Maxime.



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2022-07-30 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 12:50 [bug#56186] [PATCH] gnu: Add python-deepdish Antero Mejr via Guix-patches via
2022-07-03 11:11 ` bug#56186: " Ludovic Courtès
2022-07-30 20:54 ` Maxime Devos [this message]
2022-08-01 19:34 ` [bug#56186] [PATCH] gnu: Update python-deepdish package definition Antero Mejr via Guix-patches via

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=ffd8e30e-d3ab-84e8-2711-fb51a76a8a92@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56186@debbugs.gnu.org \
    --cc=antero@mailbox.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 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).