Conversation

Notices

1. Embed this notice
   Blaise Pabón - controlpl4n3 (blaise@hachyderm.io)'s status on Monday, 07-Apr-2025 11:14:54 JST Blaise Pabón - controlpl4n3

   in reply to

   • SynAck aka Little Sunshine :facepalm:

   @SynAck
   I am glad you asked and happy to help.
   The good news is that there is certainly a simple and reliable workflow, based on your requirements.
   I really should post a decision tree for this....
   Ok, so it seems like you are
   - ARE using tools written in Python, comprised of individual packages distributed separately.
   - are NOT writing executable code meant to be consumed by other packages

   So that narrows it down to venv and Conda.
   Sure the others work, but we're going for simplicity.
   If everything you need is available via pip, then use venv
   If some of the packages require Conda, OR, if you're already using Conda, then use that.

   • Embed this notice
     SynAck aka Little Sunshine :facepalm: (synack@corteximplant.com)'s status on Monday, 07-Apr-2025 11:14:55 JST SynAck aka Little Sunshine :facepalm:

     Just spent 30 minutes trying to figure out why my Python program using matplotlib wouldn't run, only to find out that I also needed to install PyQt6, which then seemed to require installing libxcb-cursor-dev in order to get running.

     Now I'm starting to remember why I stopped working with Linux all those years ago. :moodface: Not to mention that working with python3 on the command line and outside of an IDE (or even inside one that's not specifically designed for it) is so frustrating. The virtual environment thing is really starting to get on my last nerve.

     So, all you Python nerds out there, I have a question for you: which "virtual environment" manager should I be using? Given venv, Conda, Poetry, pyenv, pipenv, and whatever other one of the 1,000 ones I'm forgetting, how does one choose?

     And why is it this hard? This is ludicrous.