Doesn't pyenv solve?
this post was submitted on 19 Oct 2024
43 points (100.0% liked)
Linux
48331 readers
596 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Plus one for pyenv
Perhaps overkill for your use case, but uv is pretty great. I suppose you could just use it to install a local python and then add it to your path.
This was going to be my recommendation as well.
You might consider trying Miniconda, a version of Anaconda. It installs a local python environment of your choosing at a user level. https://docs.anaconda.com/miniconda/
I prefer Micromamba since it's faster at solving environments.
You can also set the solver to use libmamba if you've already installed miniconda
I Gave it a try on macOS a few days ago because brew and python is a dependencie hell and way to much workarounds to make some scripts to work properly when specific versions of packages are needed...
Miniconda actually made it work fine, without to much hassle. I'm kinda impressed.
You can install the new version of python but leave the system default python as is. You can launch a specific version of python by adding the version number
So python3.12 vs just python3
If you can install nix (you can install it per user) then you can have whatever you want in a temporary shell with nix-shell -p python
nix profile install nixpkgs#python if you want it actually installed
Home manager is also entirely user level I believe and lets you use a declarative config too
Home-manager > nix profile
Also, nix-shell is supposed to be used for debugging, and nix shell/develop for using packages without installing them
Source on the second statement? My understanding was that nix-shell is legacy for systems without flakes and nix-command enabled, and are being replaced by nix shell/run/develop
Interesting, didn't know the history of the command. But that post confirms my understanding, that nix shell/develop are the new replacements for nix-shell, with nix shell for temporary package installs and nix develop for debugging and developing
As far as I understand, they're not replacements in the same way nix profile replaces nix-env. They seem to serve a different purpose, but I don't know enough to say for certain.
of course they're not a drop-in replacement, as the cli is getting a major redesign, but as per your source
nix shell and nix develop are still experimental, so nix-shell is sticking around despite doing the same thing
it seems like they are made to fulfill the same purpose
load more comments
(5 replies)
I tried to get install instructions for home-manager and they only had them if you are already on nix?
I didnt get it
I'd try installing just regular nix (package manager, not operating system) rather than home manager, that's what I do on by Debian pi
There's an install script on their website that does it all for you
Nice! Yes I will do that. What is the difference between the 2?
Careful, there's three different terms in the mix here:
NixOS: an entire operating system, you don't need this.
nix: the nix package manager. This is what you'll need to install. look for single user install in the instructions.
home-manager: a module for nix. It's aim is to allow declarative configuration of a users' home configuration (and allow easier per-user install of packages on a global nix install).
If you want to go down the nix route, which I would recommend if you enjoy tinkering and having fine control over your system, you should start with installing nix. With that, you can already setup a shell that has the newest version of python available.
Going beyond that, I can link you some more resources, if you want c:
So "nix install" means placing a nix binary somewhere in my user $PATH?
Compile it, install it to your ~/bin.
~/.local/bin ;)
But yes, great idea.
I found a script online that installed the tar archive. For some reason that version of python still wasnt used, and invoking it with python3.12.6 or something didnt do anything
You should be able to have multiple versions with an environment manager, maybe customize your shell profile to alias python to the one you want and the other users can alias to the one they want. I’m sure there’s a better way, but I strongly dislike python every time I try to learn it because Perl was the first language I learned, ruining me for strongly opinionated languages.
@boredsquirrel
One solution could be to install uv for a single user, and use that to install and run a Python interpreter.
Can you use pyenv for the script?
Have you considered using pipx + poetry?
Can you put it in the ~/bin or something and modify the $path to go there first?
~/.local/bin you mean?
;)
Yes I tried that, and got like 6 different solutions to do this so I will see :)
Yes . Local/bin, good looking out.
Does your which program name report the right one?
Not yet fixed, no motivation
I currently use this workaround ;)
Tbh I would probably never fix it if that worked. What’s a little dongle between friends.
Not familiar with HeliumOS specifically, but for a generic atomic distro I would try layering Python temporarily, and then getting rid of it when you're done.
I see from the github ticket you need 3.10 .
There's an EPEL clone, apparently, that bundles a python3.10 package.
MAYBE this is your process:
yum* install dnf-plugins-core
yum config-manager --add-repo=https://pkgs.dyn.su/el9/base/x86_64/
yum install python3.10
Then use it like /usr/bin/python3.10 . Remove it and the repo after.
*I avoid using DidNotFinish(dnf) even though I know it's an alias.
Loooool
I thought there was no rpm-ostree but there is.
Well, lets layer some stuff!
view more: next ›