Re:Learning Go as a Python Developer: The Good and the Bad
by throwawaymaths on Monday July 18, 2022 @04:16PM
(#32143081)
Now try installing tensorflow. Treat yourself to ice cream if you get it to install without having to reinstall Linux and without borking the active project you're on.
[ Parent
| on HN ]
Re:Learning Go as a Python Developer: The Good and the Bad
by raffraffraff on Monday July 18, 2022 @04:48PM
(#32143459)
And unless things have gotten a lot better in the 2 years since I last did `pip install numpy` on ARM, prepare for a very long wait because you'll be building it from source.
Re:Learning Go as a Python Developer: The Good and the Bad
by 0x008 on Tuesday July 19, 2022 @05:03AM
(#32149159)
Sometimes if you don’t install wheel, it will also automatically fall back to source build. Very sweet.
Re:Learning Go as a Python Developer: The Good and the Bad
by Gilboboy on Tuesday July 19, 2022 @02:57AM
(#32148346)
There's a precompiled package for ARM these days.
Re:Learning Go as a Python Developer: The Good and the Bad
by codethief on Tuesday July 19, 2022 @08:49AM
(#32150716)
Does it come with GPU support?
Re:Learning Go as a Python Developer: The Good and the Bad
by derac on Monday July 18, 2022 @05:04PM
(#32143679)
The major issues you'll see involve library version mismatches. It's a very good idea to use venv with these tools since there are often mismatches between projects.
Re:Learning Go as a Python Developer: The Good and the Bad
by throwawaymaths on Tuesday July 19, 2022 @12:31AM
(#32147562)
Tensorflow sometimes is pinned to Nvidia drivers, and protobuf. And I think it has to be system level unless you reaaaaally want to fiddle with the internals.
Re:Learning Go as a Python Developer: The Good and the Bad
by smeagull on Monday July 18, 2022 @07:14PM
(#32145345)
I'd be too fat from all that icecream.
Re:Learning Go as a Python Developer: The Good and the Bad
by throwawaymaths on Tuesday July 19, 2022 @12:33AM
(#32147576)
Ok. I know two companies that exist because of this problem.