Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.
bio
Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.
upgrading your base image won’t affect your python packages
Surely if upgrading python will affect your global python packages it will also affect your venv python packages?
you can use multi stage builds to create drastically smaller final images
This can also be done without using venv’s, you just need to copy them to the location where global packages are installed.
I don’t think they have anything to do with each other, it looks like prefix.dev uses conda packages.
Yeah it is, eventually they want UV to have feature parity with rye and rye will basically just be a pointer to UV
Early on uv was only trying to replace pip. This latest update is a big step towards becoming a poetry (and pyenv/pipx) replacement too.
Yeah I agree, I am sure they are missing some obscure stuff. But in practise it has everything that I use and there has been no need for me to touch flatpak/appimage/snap
object oriented
Python does have OOP but you are not at all forced to use it. You can write code in a functional or even procedural style.
typing
I do hate that python doesent have proper support for typing but I think weakly typed variables will actually help beginners as it is less to think about to start off with.
indentation
I think there are pros and cons here. In other languages it is considered good style to use indentation anyway.
I’m sure it is difficult to teach a large class like that though. It was hard enough for me to learn with a much more favourable teacher to student ratio than you probably have. Sorry but honestly I do sympathise with admin as well.
yep, I mean a GUI based software centre
NixOS:
I think it will easily be the number 1 distro if/when they can :
One thing I haven’t seen mentioned is that not moving between mouse and keyboard so much reduces the risk of getting an RSI. So even if it didn’t make you faster it would still probably be worth it to find a keyboard based workflow.
I use Helix and would suggest you try it (at least to start off with) as it is easier to learn than vim and does not require plugins or a complex config. To answer your question I will go from the less to more advanced/complex:
x
then d
to select a line (pressing N times will select N lines) and delete it (delete will also copy to the clipboard)p
to paste in a newg
then d
when on a function/class usage.g
then r
.
to select the entire files contentss
to searchv
then g
then l
to select the rest of the linespace
+y
to copy to the system clipboard.There is actually a helix community on programming.dev: helix@programming.dev
What is the app?
Why? It is the same power dynamic as any other open source project that is primarily built by a company.
From what I read in the HN thread the token is only used for governance (and possibly also fundraising), it is not baked into the actual platform. I am happy to be corrected though if anyone knows more/has more details.
I agree that Forgejo looks good as well and is likely more usable than Radicle right now. But I do think there is value at looking at P2P solutions.
From what I read in the HN thread the token is only used for governance (and possibly also fundraising), it is not baked into the actual platform. I am happy to be corrected though if anyone knows more/has more details.
This actually sounds really promising!
Edit: here is a blog post from the creator of rye talking about rye and UV: https://lucumr.pocoo.org/2024/2/15/rye-grows-with-uv/
Sorry about this. I just found the video interesting when it popped up on my feed.
I don’t know about the history of this creator, I just found this particular video interesting when it popped up. Sorry if this creator is known to be untrustworthy.
Thank you Ategon and all the other admins for the work you are doing to make this place great.
If you do multi stage builds (example here) it is slightly easier to use venvs.
If you use the global environment you need to hardcode the path to global packages. This path can change when base images are upgraded.