unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Prototype for using Guix with python packages
Date: Wed, 07 Sep 2016 16:01:12 +0200	[thread overview]
Message-ID: <87fupbn713.fsf@gnu.org> (raw)
In-Reply-To: <4174c012-8e2b-d6f2-8387-031e309b7daf@cbaines.net> (Christopher Baines's message of "Tue, 6 Sep 2016 07:26:23 +0100")

Hello!

Christopher Baines <mail@cbaines.net> skribis:

> For a few months now, I've been assembling a prototype for how packages
> could be produced for software released as Python source distributions
> (sdists) [1].

Woow, quite an achievement!  Do you know how many of the automatically
generated packages built from source flawlessly?

IIRC, ‘guix import pypi’ currently produces templates that can require
extra tweaks, although that was improved by reading metadata from
Wheels.

How does sdist metadata differ from PyPI or Wheels metadata?  Is it
generally more complete, or of better quality?

> I will also try to look at how what I have been doing could be used to
> improve the Guix PyPI importer and the Python build system, as well as
> submit the packages that are currently just in the guix-env.scm file in
> the repository (pyguile, libsolv) for inclusion in Guix.

That would be awesome!  Anything towards making the output of ‘guix
import’ work out of the box would be great.

> I'm quite excited by the possibilities offered by approaches like this,
> and was wondering if anyone has feedback, questions, opinions, or if
> anyone is working on something similar?

That reminds me of the “recursive importer” that has been discussed a
few times and is currently implemented (but not in master yet) for the
CRAN and NPM importers.  Perhaps your work could be somehow integrated
to get a recursive PyPI/sdist importer?

An idea would be to automatically put all the imported packages into,
say, ~/.cache/guix/python, and add that to GUIX_PACKAGE_PATH.  Then we
could run “guix import pypi --update” to update it, or something like
that.

Thanks for sharing!

Ludo’.

  reply	other threads:[~2016-09-07 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  6:26 Prototype for using Guix with python packages Christopher Baines
2016-09-07 14:01 ` Ludovic Courtès [this message]
2016-09-10 13:09   ` Christopher Baines
2016-09-11 13:43     ` Ludovic Courtès
2016-09-11 14:25       ` Christopher Baines
2016-09-11 20:34         ` 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

  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=87fupbn713.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.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 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).