guix pack error with python packages

Hello guix,

I’m trying to deploy a test set of python packages to a remote server,

using the following guix pack command (latest guix, as for now)

guix pack -R --compression=xz --save-provenance \

-S /.guix-profile/bin=bin -S /.guix-profile/share=share \

-S /.guix-profile/etc=etc -S /.guix-profile/lib=lib \

-S /.guix-profile/include=include

The resulting file.tar.xz is sent to the server with

scp file.tar.xz server:/dir1/dir2/.

Then, when I

ssh server

cd /dir1/dir2

I do a

tar xf file.tar.xz

At this point, a ’ls /dir1/dir2’ shows, as expected

.guix-profile

gnu

file.tar.xz

Now, when I just (PYTHONPATH is empty at this point)

/dir1/dir2/.guix-profile/bin/python3 -c \

"import sys; print(sys.path)"

I get

/dir1/dir2/hj...python...

/dir1/dir2/hj...numpy...

/dir1/dir2/hj...matplotlib...

instead of

/dir1/dir2/gnu/store/hj...python...

/dir1/dir2/gnu/store/hj...numpy...

/dir1/dir2/gnu/store/hj...matplotlib...

so that when I

/dir1/dir2/.guix-profile/bin/python3 -c "import numpyt"

I get an error

ModuleNotFoundError: No module named 'numpy'

If, however, I

export GUIX_PROFILE=/dir1/dir2/.guix-profile

source $GUIX_PROFILE/etc/profile

export PYTHONPATH=$GUIX_PYTHONPATH

and then

/dir1/dir2/.guix-profile/bin/python3

I have

Error processing line 1 of

/dir1/dir2/.guix-profile/lib/python3.9/site-packages/matplotlib-3.5.2-py3.9-nspkg.pth:

Trying to ’import numpy’ gives

Traceback (most recent call last):

File "<stdin>", line 1, in <module>

File "/dir1/dir2/.guix-profile/lib/python3.9/site-packages/numpy/__init__.py", line 110, in <module>

import warnings

ModuleNotFoundError: No module named 'warnings'

Am I doing something wrong ? Is this a bug ?

Thanks,

Cayetano Santos

Hi Cayetano,

Cayetano Santos via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

This is most likely [1], which hasn't been fixed yet but I have a patch

to that effect. The problem is that it would cause a lot of rebuilds so

I haven't sent it yet, I'll send it after the core-updates merge.

[1] https://issues.guix.gnu.org/53258

mid: 67e7d225-f824-b691-7125-6b37abef8bb0@felsoci.sk

Best,

--

Josselin Poiret

Hi Josselin,

Josselin Poiret <dev@jpoiret.xyz> writes:

If you send it *after* the core-updates merge (to core-updates)? It's

going to be quite a while before it lands to master. Perhaps you could

send it now? core-updates is the right branch for mass rebuilds.

--

Thanks,

Maxim

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

I think we are trying to move away from the massive core-updates branch

and rather work with feature branches instead, although the pending

core-updates merge is blocking the change for now. I don't want to add

yet more work for people courageously working on core-updates right now.

Best,

--

Josselin Poiret

Hi Josselin,

Josselin Poiret <dev@jpoiret.xyz> writes:

Perhaps I'm out of the loop, but in my book the main branches should

never close. If there's a need to freeze the state of one the three

main branches new development branches can be created. This was

discussed in the past.

--

Thanks,

Maxim

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

I don't think there was a freeze for core-updates this time, commits are

still rolling in on the core-updates branch.

Best,

--

Josselin Poiret

Hi,

Just for the record, I fixed the problem with

export PYTHONPATH=$GUIX_PYTHONPATH:/path-to/.guix-profile/lib/python3.10/:/path-to/.guix-profile/lib/python3.10/site-packages/:/path-to/.guix-profile/lib/python3.10/lib-dynload

I’m using an up to date guix. Now I can import and use all the python

libraries with no problem.

Thanks,

Cayetano