News for hackers. Stuff that matters.
Re:Learning Go as a Python Developer: The Good and the Bad by smeagull on Monday July 18, 2022 @07:12PM (#32145331)
The real issue is that you can't have multiple versions installed at the same time.

if you could import numpy==3.2 it'd solve many problems.

Re:Learning Go as a Python Developer: The Good and the Bad by thinker5555 on Monday July 18, 2022 @07:34PM (#32145548)
Granted, I'm more of a hobbiest than a dev, but I think this is part of the problem that virtualenvs are supposed to help solve. One project (virtualenv) can have numpy==3.2, and another can have numpy==3.1. Maybe I'm naive, but it seems like having a one project with multiple versions of numpy being imported/called at various times would be asking for trouble.
Re:Learning Go as a Python Developer: The Good and the Bad by Spivak on Monday July 18, 2022 @08:36PM (#32145977)
The thing you can’t do is solve for this situation.

    A depends on B, C
    B depends on D==1.24
    C depends on D==2.02
There should in an super ideal world be no problem with this. You would just have a “linker” that inserts itself in the module loader that presents different module objects when deps ask for “D” but it hasn’t happened yet.
Re:Learning Go as a Python Developer: The Good and the Bad by goodpoint on Tuesday July 19, 2022 @07:36AM (#32150131)
That's a feature, not a bug.
Re:Learning Go as a Python Developer: The Good and the Bad by smeagull on Thursday July 21, 2022 @08:47AM (#32178662)
It's really not. I can't install tensorflow more than 10 times before I'm done. Virtualenvs are not fit for purpose.