FYI on the latest Ubuntu it's the exact same stuff: pip won't let you install shit in your global or user namespace. You're supposed to use a venv.
Of course Nix also offers other alternatives, just read the nix page on python.
>who the fuck dictated this
Thousands of retard like you who'd just install anything into their user namespace for years and send emails about "HURRDURR WHY PYTORCH NO WORK PLEASE FIX"
>Be OP >Install a distro he is to dumb for >Blames distro when its a design choice because distro devs know the average user is as retarded as him >I KNOW WHAT I'M DOING, I AM A BIG BOY WHO BROWSES /misc/ AND LULZ ALL DAY LONG!
Why dont you fuck up the board some more with another anti-Rust thread(which you are also to dumb for).
There's pipx to automatically manage your python environments
By default each package with it's dependencies is separated but you can inject them if you need to.
I've just been passing --break-system-packages on arch. It does break system packages sometimes, i don't know how because i'm not giving it sudo, but every time i've fixed it by deleting the conflicting file
> i don't know how because i'm not giving it sudo,
That's not the reason it breaks system packages. It's because your user pip installed packages have higher priority in your path than system packages.
Now imagine package A is dependent on package B version 1.0.0. Now you install package B version 2.0.0 with pip. When system package A tries to load package B it gets version 2.0.0 with a different API and crashes when it tries to call a deprecated function.
Just use venv for projects and pipx for CLI tools.
>It's because your user pip installed packages have higher priority in your path than system packages.
this hasn't been problem for me >Just use venv for projects and pipx for CLI tools.
i don't think i will
>It's because your user pip installed packages have higher priority in your path than system packages.
this hasn't been problem for me >Just use venv for projects and pipx for CLI tools.
i don't think i will
It wouldn't even be a dumb policy if they had a halfway decent replacement. Look at node: everyone uses package.json with zero complaints, because it just werks. Literally just copy that to the letter, make it official, and people will use it by choice instead of needing their arm twisted.
>I know what I'm doing
No you don't. Otherwise you wouldn't be using a declarative Linux distro. Its meant for declarative development environments. You're basically the software equivalent of a vegan complaining he was served meat when he ordered a steak dinner.
And as other anons have said more recent versions of python require a venv anyways.
The problem is documentation is dog shit or now outdated. Python makes major changes with every minor update that completely fucks with everything and makes any tutorial guide outdated while also providing little to no documentation on what the fuck they added or changed.
Holy shit it drives me insane how much reliance on python Linux has.
No, I mean you don't need NixOS to use Nix. I use Nix all the time in hostile environments (old as fuck distros, no sudo rights, etc.) to get proper up to date tooling
Any nixbros still itt? Any up-to-date guide on setting it up? Last time I tried you had all this other shit like nix home flakes and whatever that made everything easier but they weren't even fucking mentioned in the wiki.
I'd much rather read a written guide over a video but as long as it's good I'll take it.
>https://nixos-and-flakes.thiscute.world/
Seems like this is the bare minimum I need to setup my stuff without wasting time with suboptimal shit then.
Thanks
Thanks
>installs a OS that handles packages in a strict deterministic way so shit does not break >is confused that it is handling packages in a strict deterministic way
How can you be this retarded?
Who are you quoting
FYI on the latest Ubuntu it's the exact same stuff: pip won't let you install shit in your global or user namespace. You're supposed to use a venv.
Of course Nix also offers other alternatives, just read the nix page on python.
same with arch
why
who the fuck dictated this and never asked me
>who the fuck dictated this
Thousands of retard like you who'd just install anything into their user namespace for years and send emails about "HURRDURR WHY PYTORCH NO WORK PLEASE FIX"
why do they do this to me...
I don't want venv...
Use go
>Be OP
>Install a distro he is to dumb for
>Blames distro when its a design choice because distro devs know the average user is as retarded as him
>I KNOW WHAT I'M DOING, I AM A BIG BOY WHO BROWSES /misc/ AND LULZ ALL DAY LONG!
Why dont you fuck up the board some more with another anti-Rust thread(which you are also to dumb for).
calm down troon
AIEEEEEEEEE A NEWFAG FELL FOR THE CONSTANT YEAR-WIDE SHILLING CAMPAIGN AND IS UNSATISFIED WITH MY OBTUSE OS!!! AIEEEE SAVE ME HRTMAAA'M
that's the thing
I don't want to use venv
>I know what I'm doing
I guess that's settled then
There's pipx to automatically manage your python environments
By default each package with it's dependencies is separated but you can inject them if you need to.
That's just how it is now, it's a fairly recent change
I've just been passing --break-system-packages on arch. It does break system packages sometimes, i don't know how because i'm not giving it sudo, but every time i've fixed it by deleting the conflicting file
> i don't know how because i'm not giving it sudo,
That's not the reason it breaks system packages. It's because your user pip installed packages have higher priority in your path than system packages.
Now imagine package A is dependent on package B version 1.0.0. Now you install package B version 2.0.0 with pip. When system package A tries to load package B it gets version 2.0.0 with a different API and crashes when it tries to call a deprecated function.
Just use venv for projects and pipx for CLI tools.
>It's because your user pip installed packages have higher priority in your path than system packages.
this hasn't been problem for me
>Just use venv for projects and pipx for CLI tools.
i don't think i will
>It does break system packages sometimes
>this hasn't been problem for me
IQ issue
Are you illiterate? There are two different ways it can break system packages. The one I've faced is trivially fixed.
>just randomly delete stuff bro
You're the reason pip implemented that new policy
It wouldn't even be a dumb policy if they had a halfway decent replacement. Look at node: everyone uses package.json with zero complaints, because it just werks. Literally just copy that to the letter, make it official, and people will use it by choice instead of needing their arm twisted.
>requirements.txt
To be fair that's a pretty shit decision though
Instead of fixing their package manager they simply ask users for more disk space
What fix? If you use a language-specific package manager on top of the system one without compartmentalization, things will invariably go to shit.
just do whatever rust is doing with cargo
Not using the system package manager at all?
what?
NOT USING THE SYSTEM PACKAGE MANAGER AT ALL?
WHAT?
just use pipx
do a venv and then use pip in there
How kind of them to include a drawing of the average Linux user in their logo.
>I know what I'm doing
Clearly you don't
>I know what I'm doing
No you don't. Otherwise you wouldn't be using a declarative Linux distro. Its meant for declarative development environments. You're basically the software equivalent of a vegan complaining he was served meat when he ordered a steak dinner.
And as other anons have said more recent versions of python require a venv anyways.
Write a flake.nix like you should, then you can use pip or whatever the fuck you want.
venvs arent hard just get on with is
I'm more of a mamba man myself
The problem is documentation is dog shit or now outdated. Python makes major changes with every minor update that completely fucks with everything and makes any tutorial guide outdated while also providing little to no documentation on what the fuck they added or changed.
Holy shit it drives me insane how much reliance on python Linux has.
what about venv isn't documented
Use a nix-shell or flake.
I like nixos, but sometimes there's a lot of headache doing things the nix way.
Based Nixxers.
Stop polluting your environment with that shit.
Python development still blows with nix. Poetry2nix mostly just werks for me.
I hate python so goddamned much.
In a team of ten devs with five different distros deploying to even more servers this shit never works
Give me a foolproof way, LULZ.
>Give me a foolproof way, LULZ.
Yeah, nix
No. The whole point is that it needs to work regardless of distro.
Yeah, nix
REEEEEEEEEEEE
you can't argue against nix users
they are the same people who use emacs too
you can't win
you doomed
give up
No, I mean you don't need NixOS to use Nix. I use Nix all the time in hostile environments (old as fuck distros, no sudo rights, etc.) to get proper up to date tooling
>Nix
I see. Thanks for the info!
containers
A good solution for apps.
What about scripts?
-v /:/
Any nixbros still itt? Any up-to-date guide on setting it up? Last time I tried you had all this other shit like nix home flakes and whatever that made everything easier but they weren't even fucking mentioned in the wiki.
I'd much rather read a written guide over a video but as long as it's good I'll take it.
just opened the wiki, not a SINGLE mention of the word "flakes" in the whole fucking page.
Seriously, what the fuck.
https://nixos.org/manual/nixos/stable/
https://nixos-and-flakes.thiscute.world/
https://nix.dev/recommended-reading
Yeah,
>https://nixos-and-flakes.thiscute.world/
Seems like this is the bare minimum I need to setup my stuff without wasting time with suboptimal shit then.
Thanks
Thanks
Also ChatGPT can help a lot
You're meant to use Gentoo, I don't know how you ended up using a shitty dying meme
>installs a OS that handles packages in a strict deterministic way so shit does not break
>is confused that it is handling packages in a strict deterministic way
How can you be this retarded?