python-pytorch collides with tensorflow

  • Open
  • quality assurance status badge
Details
3 participants
  • Cayetano Santos
  • Ludovic Courtès
  • zimoun
Owner
unassigned
Submitted by
Cayetano Santos
Severity
normal
C
C
Cayetano Santos wrote on 7 Dec 2021 09:41
Error installing pytorch and tensorflow
(address . bug-guix@gnu.org)
yu1bl1skdkn.fsf@inventati.org
Hi guix,

By just issuing a

guix install python-pytorch tensorflow

I get a conflict error with python-protobuf (3.6.1 and 3.12.4).
However, when I

guix shell --container python-pytorch tensorflow

I manage to create an environment with no issue.

Finally, with ’guix pack ...’ I get the same error as before.

Best,

Cayetano Santos
Z
Z
zimoun wrote on 7 Dec 2021 11:16
(address . cayetano.santos@inventati.org)(address . 52348@debbugs.gnu.org)
CAJ3okZ3xtSpHk-Sebs5vHoYyK4jezqSyk2zvNu6AyWdHNfbHFg@mail.gmail.com
Hi,

On Tue, 7 Dec 2021 at 09:47, Cayetano Santos via Bug reports for GNU
Guix <bug-guix@gnu.org> wrote:

Toggle quote (6 lines)
> By just issuing a
>
> guix install python-pytorch tensorflow
>
> I get a conflict error with python-protobuf (3.6.1 and 3.12.4).

Yes, indeed. tensorflow propagates python-protobuf@3.6. And
python-pytorch propagates onnx which itself propagated
python-protobuf@3.12. As the error message says. :-)


Toggle quote (6 lines)
> However, when I
>
> guix shell --container python-pytorch tensorflow
>
> I manage to create an environment with no issue.

Oh, yes it works. However, note that tensorflow is probably not
compatible with the current Numpy version.


Hum, I do not know what is expected. :-) Is it that 'shell' does as
'install' does? Or contrary? Well, I thought that "shell" was doing
the same thing as "install" but the profile was just marked as
temporary.


Cheers,
simon
L
L
Ludovic Courtès wrote on 22 Dec 2021 23:50
control message for bug #52348
(address . control@debbugs.gnu.org)
87ee64xnj8.fsf@gnu.org
retitle 52348 python-pytorch collides with tensorflow
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 52348@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 52348
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch