Skip to main content

Seriously. How do #Python devs get any work done?

I'm only working in it occassionally. In a broad range of projects/versions.

I honestly spend at least half my time on resolving version stuff, getting pip to work in this venv/pipenv/whateverenv, fixing pyright again.

I mean, this is bad with Ruby and insane in JavaScript. But Python pushes it to another level alltogether for me.

Is it because I'm on Ubuntu LTS? Is it that I only occasionally work on Python projects?

#python
in reply to Bèr Kessels 🐝 🚐 🏄 🌱

Aracnus
Aracnus
•
@Bèr Kessels 🐝 🚐 🏄 🌱 , I use #miniconda (docs.anaconda.com/miniconda/) and it makes everything much easier. Just create an environment, put everything you need there (via pip or conda commands) and that's it. You can even have more environments, with completely different libraries.
#miniconda @Bèr Kessels 🐝 🚐 🏄 🌱
in reply to Aracnus

Bèr Kessels 🐝 🚐 🏄 🌱
Bèr Kessels 🐝 🚐 🏄 🌱
• •
@aracnus that's another thing I dislike in Python. There are at least four ways to solve all this. And even more alternatives that don't work (anymore).
@Aracnus
in reply to Bèr Kessels 🐝 🚐 🏄 🌱

Aracnus
Aracnus
•

@Bèr Kessels 🐝 🚐 🏄 🌱 , in fact, it's the same way, in background you have virtual environments and pip. The problem with Python in any GNU/Linux distro is that the versions of the libraries in distro packages are usually much older than the latest versions. So, if you need a newer library, you have to install it isolated and then the mess begins. If you want to keep your python environment simple, the best to do to install only the basic packages (preferable no libraries packages) and manage all the libraries via pip. This will avoid a lot of conflicts.

This is what miniconda does. It simplify creation of virtual environments and libraries installations. But you can do it all by hand too, if you want.

@Bèr Kessels 🐝 🚐 🏄 🌱

This website uses cookies to recognize revisiting and logged in users. You accept the usage of these cookies by continue browsing this website.

⇧