▲ 362 ▼ xkcd #1987: Python Environment (xkcd.com) submitted 3 years ago by jnovinger@programming.dev to c/programmer_humor@programming.dev 73 comments fedilink hide all child comments
[+] oscar@programming.dev 1 point 3 years ago (3 children) [deleted] permalink fedilink source parent hideshow 6 child comments replies: [–] stOneskull@programming.dev 2 points 3 years ago i've moved to just using conda environments. i find it's a lighter load on my old brain. permalink fedilink source parent [–] infeeeee@lemm.ee 2 points 3 years ago I love this workflow because it has only two prerequisites: python and pip. It works on windows, linux, any vm or container. Pipenv requires some setup, while this should work everywhere. In powershell you have to use ./.venv/bin/acticate.ps1 but that's the only difference. permalink fedilink source parent [–] Mikina@programming.dev 1 point 3 years ago (1 child) What did you not like on pipenv in comparison to venv? I was always avoiding venv because it was, as you said, manual work and it was too much effort to again google what was the order of commands and parameters to start a venv, which is not an issue in pipenv, since you just pipenv install what you need. permalink fedilink source parent hideshow 2 child comments replies: [+] oscar@programming.dev 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Mikina@programming.dev 1 point 3 years ago I only use python as a go-to scripting language when I need to quickly automate something or write a quick throwaway script that requires an SDK, since there's a python library for almost anything and doing it in powershell would be too much aditional work. But it does make sense that for CI you only need to figure out the venv setup once and you're done, so it may be a better solution. permalink fedilink source parent
[–] stOneskull@programming.dev 2 points 3 years ago i've moved to just using conda environments. i find it's a lighter load on my old brain. permalink fedilink source parent
[–] infeeeee@lemm.ee 2 points 3 years ago I love this workflow because it has only two prerequisites: python and pip. It works on windows, linux, any vm or container. Pipenv requires some setup, while this should work everywhere. In powershell you have to use ./.venv/bin/acticate.ps1 but that's the only difference. permalink fedilink source parent
[–] Mikina@programming.dev 1 point 3 years ago (1 child) What did you not like on pipenv in comparison to venv? I was always avoiding venv because it was, as you said, manual work and it was too much effort to again google what was the order of commands and parameters to start a venv, which is not an issue in pipenv, since you just pipenv install what you need. permalink fedilink source parent hideshow 2 child comments replies: [+] oscar@programming.dev 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Mikina@programming.dev 1 point 3 years ago I only use python as a go-to scripting language when I need to quickly automate something or write a quick throwaway script that requires an SDK, since there's a python library for almost anything and doing it in powershell would be too much aditional work. But it does make sense that for CI you only need to figure out the venv setup once and you're done, so it may be a better solution. permalink fedilink source parent
[+] oscar@programming.dev 1 point 3 years ago (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Mikina@programming.dev 1 point 3 years ago I only use python as a go-to scripting language when I need to quickly automate something or write a quick throwaway script that requires an SDK, since there's a python library for almost anything and doing it in powershell would be too much aditional work. But it does make sense that for CI you only need to figure out the venv setup once and you're done, so it may be a better solution. permalink fedilink source parent
[–] Mikina@programming.dev 1 point 3 years ago I only use python as a go-to scripting language when I need to quickly automate something or write a quick throwaway script that requires an SDK, since there's a python library for almost anything and doing it in powershell would be too much aditional work. But it does make sense that for CI you only need to figure out the venv setup once and you're done, so it may be a better solution. permalink fedilink source parent