From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Roy Lemmon <roy@roylemmon.com>,
sirgazil <sirgazil@zoho.com>
Subject: Re: Setting up a python environment
Date: Mon, 11 May 2020 10:31:41 -0400 [thread overview]
Message-ID: <4B6E6067-059E-42A0-89D9-C940A5A06B31@lepiller.eu> (raw)
In-Reply-To: <CAH5rZC43U3nSJ7W=sxw-ry_2ORJomfy=HNMUXsrnVAeSTbB8Zw@mail.gmail.com>
Le 11 mai 2020 10:09:40 GMT-04:00, Roy Lemmon <roy@roylemmon.com> a écrit :
>Thanks sirgazil. That is very helpful.
>
>Yes, it might be that astropy has many dependencies.
>
>I will take a look at that video and also get a better handle on
>packaging.
>
>Cheers
>Roy.
>
>
>On Mon, 11 May 2020, 14:56 sirgazil, <sirgazil@zoho.com> wrote:
>
>> ---- On Mon, 11 May 2020 07:34:09 -0500 Roy Lemmon
><roy@roylemmon.com>
>> wrote ----
>> > Hi,
>> >
>> > I would like to ask about the general philosophy of setting up a
>python
>> > environment under guix.
>> >
>> > For other linux systems I have used pip to manage python packages
>and
>> > libraries.
>> >
>> > In guix is the idea that guix replaces pip for managing packages
>and
>> > libraries ?
>>
>> I think so, yes, ideally.
>>
>> > So I would create a python-package for any missing python
>> > packages ?
>>
>> Yes.
>>
>> > In the guix package lists, I can find many of the python
>> > libraries but there are a few missing that I would like, eg.
>astropy -
>> an
>> > astronomy analysis library. So should I be creating a guix package
>for
>> that
>> > rather than installing with pip ?
>>
>> That's the idea, yes: to have all Python packages available in Guix.
>That
>> way, if your projects depend on Python packages and non-Python
>packages,
>> you can specify all the requirements of your projects conveniently in
>a
>> Guix manifest file (instead of having a requirements file for pip and
>> another requirements file for some OS package manager, and possibly,
>> another requirements file for another programmnig language used in a
>> project).
>>
>> In practice, though, your projects could require many packages that
>are
>> not yet in Guix. For example, astropy could depend on other packages
>that
>> are not available, and those packages depend on other packages that
>are not
>> available, and so on. To package them all would be a job in itself,
>and you
>> would not have time to work on your project. So, depending on your
>> specific case, you might still need to use Python virtual
>environments and
>> pip to get things done. For the latter you can use Python's venv, or
>> poetry, or other tools that are already available in Guix for
>managing
>> Python projects and environments.
>>
>> I recommend to watch the https://guix.gnu.org/videos/ for an
>introduction
>> to packaging.
>>
>>
>>
>>
>> ---
>> https://sirgazil.bitbucket.io/
>>
>>
>>
>>
Guix also has a cool import feature that might help you package missing paekages. You thould try 'guix import pypi -r astropy'.
next prev parent reply other threads:[~2020-05-11 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 12:34 Setting up a python environment Roy Lemmon
2020-05-11 13:55 ` sirgazil
2020-05-11 14:09 ` Roy Lemmon
2020-05-11 14:31 ` Julien Lepiller [this message]
2020-05-11 14:45 ` Roy Lemmon
2020-05-11 14:51 ` zimoun
2020-05-11 15:01 ` Roy Lemmon
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=4B6E6067-059E-42A0-89D9-C940A5A06B31@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=roy@roylemmon.com \
--cc=sirgazil@zoho.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.
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).