From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Marius Bakke <marius@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Profiles for Python projects
Date: Fri, 19 Jun 2020 11:04:00 +0200 [thread overview]
Message-ID: <103bced2-86a5-9215-3ae8-38654f8d69e8@posteo.de> (raw)
In-Reply-To: <875zbodnfy.fsf@gnu.org>
Hi Marius!
That makes sense! I guess the GUIX Python packages are each in their own
location, so GUIX has to do this. I did not pay enough attention to the
PYTHONPATH thing.
… testing right now …
And it works! Thanks!
Regards,
Zelphir
On 19.06.20 00:22, Marius Bakke wrote:
> Hi Zelphir,
>
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>
>> I create a profile with that and it works fine:
>>
>> guix package --manifest="manifest.scm" --profile="${GUIX_EXTRA_PROFILES}"/my-env/my-env
>>
>> Then I do the sourcing:
>>
>> GUIX_PROFILE="${GUIX_EXTRA_PROFILES}/my-env/my-env"; source "${GUIX_PROFILE}/etc/profile"
> [...]
>
>> I also get a path in the profile I created. So far all seems to just
>> work. However, then I hit a snag when trying to run the tests of the
>> project:
>>
>> LOG_LEVEL="DEBUG" PYTHONPATH="$(pwd)/my_project" python3 -m pytest -m "my_test_marker" -s -vvv
>>
>> I now get the error:
>>
>> No module named pytest
> This is because you are overriding PYTHONPATH. If you run it as ...
>
> LOG_LEVEL="DEBUG" PYTHONPATH="$(pwd)/my_project:$PYTHONPATH" python3 -m pytest -m "my_test_marker" -s -vvv
>
> ... you might have better luck. Guix relies on PYTHONPATH to make
> Python modules available because there is no single site-packages
> directory like in some other distributions.
>
> HTH!
> Marius
prev parent reply other threads:[~2020-06-19 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 16:53 Profiles for Python projects Zelphir Kaltstahl
2020-06-18 22:22 ` Marius Bakke
2020-06-19 9:04 ` Zelphir Kaltstahl [this message]
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=103bced2-86a5-9215-3ae8-38654f8d69e8@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=help-guix@gnu.org \
--cc=marius@gnu.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.
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).