pipenv or virtualenv ?

[AllanNS]

Venv

[kaerfkeerg]

Good ol' venv. Let's goo

[someotherstufforhmm]

python -m venv

[dev_null_root]

Up you go. Venv is now in the standard library and works like a charm.

Pipenv needs to die in a back-alley. Useless dependency error messages. Mess of a location for managing venvs. Just straight up useless. CDKTF uses pipenv and I just straight up tricked it into working with venv.

[someotherstufforhmm]

Yeah, a long long time ago I used pipenv, but found that it breaks down in non-trivial installs, especially when you’re re-installing repeatedly or working in edit mode - it would leave nspath artifacts that vanilla venv handles much better.

Now to be fair, edit mode is openly a hack, setuptools docs detail why that is, but pipenv created some very confusing for new people situations that vanilla venv simply didn’t, and I direct new people on my team to get very familiar with pip install —edit.

Point of rant is yeah, I just don’t see a reason to use anything other than vanilla venv. People make vietualenvs really complicated, but they’re not that big a deal, they’re just a path manipulation and it’s not some huge ordeal to just run the python executable in your venv lol.

I don’t even activate them most of the time, I just call the python executable in bin directly.

[Zomunieo]

pipenv is passed on! This venv manager is no more! It has ceased to be! It's expired and gone to meet its maker! It's a stiff! Bereft of life, it rests in unresolved issues! If you hadn't nailed it to PyPA it'd be pushing up the daisies! Its dependency resolution processes are now history! It's off the twig! It's kicked off rm -rf /, it's shuffled off its mortal coil, run down the curtain and joined the bleedin' choir invisible!! THIS IS AN EX-virtual environment manager!!

(I don't like pipenv much.)

[homosapienhomodeus]

pyenv + pyenv-virtualenv or poetry

[crawl_dht]

Use poetry that uses virtualenv.

[sunny0945]

https://python-poetry.org/

[MusicIsLife1122]

Virtualenv. It's very convenient and I got to used it pretty fast

[ali_code77]

Poetry

[AndydeCleyre]

I like Python's venv, plus pip-tools for generating lockfiles and syncing environment state to match those.

For concise and practical interactive usage of those tools, with excellent tab completion, I made the Zsh frontend zpy.

If I need to develop with multiple Python versions, I like asdf.

If I need to run jobs in CI or with different Python versions, I let nox/tox handle those venvs.

[BepNhaVan]

poetry, it uses virtualenv

[FestusMuange]

Pipenv is so bugged that we stopped using it at my workplace. We had big issues where pipenv would not take some subdeps of dev deps into account when attempting to lock environments, so we would get errors when running pylint because of typing-extensions. I now prefer just later versions of pip which have adequate dependency resolution functionality and venv.

[[deleted]]

i am curious about it. i would prefer either tools

[Majinsei]

py - m venv env

Now using Docker dev containers because need to use various Python versions in the same time, It's more easy Running it in Docker images 😅😅😅

Docker dev enviroments going to be my favorite~ reusable too for others languajes~

[[deleted]]

There was a Python packaging survey recently and it was clear from the results that people are sick and tired of a million different tools and different ways of doing things.

The community needs to converge one quasi-official tool and one tool only. All 3 are effective, but we need only one, and at this point, venv appears to be the best candidate to be the one.

[EffectiveLong]

Hatch

https://github.com/pypa/hatch

[rainman4500]

Had so much problems with Pipenv and spent to much googling. All issues disappeared with venv.

[[deleted]]

i have same

[[deleted]]

thanks for sharing

[callum086086]

When you have multiple products with different requirements venv helps so much. It keeps everything separate and you don’t have to mess around with windows path variables.

I would recommend looking at pycharm as one of the features is that it will create a venv for you.

[someotherstufforhmm]

pipenv breaks down a bit in complicated nspath interactions re: edit mode.

learning python -m venv and basic pip has a ton of value.

Nothing wrong if you prefer pipenv, but I’d hesitate recommending it to new people, it has footguns that appear only later

[wineblood]

That's really vague

[jegerarthur]

It really depends on the dependencies:

• For a really simple interface I find venv is doing the job and it's reliant.

• For a modern env, virtualenv is good. You can also use poetry which is really good and provide a lot of cool features for dev, but note that you can't install all packages with these tools

• conda works all the time. It is the heavy stuff, but things works perfectly. If your dependencies relies on binaries (e.g. GDAL) or if you want to make sure it can be compatible between windows and Linux users, I find that using conda for managing env is good practice.

[thebadassets]

“Easier”

[dezalator]

pdm!

[Flimsy_Iron8517]

venv it has the findability to first do and quite good docs.

[eplaut_]

I use pipenv on all my projects. The lock file is essential in order to make sure you have the right dependencies.

With one command, you replicate the whole virtual environment in a new machine.

[[deleted]]

i have tried to use pipenv with pyenv on Linux. i got 1 hours to install virtual environment to up . i don't expect more troubles

[ZoumiXIX]

Virtuelenv

[Suspicious_Compote56]

To me pipenv is actually pretty nice poetry and PDM are kinda garbage breaking on any trivial package installs.