erictleung,
@erictleung@mastodon.social avatar

I'm more of an R programming who uses Python when it fits better.

and being seven years late, I didn't realize the built-in Python virtual environment, venv, got deprecated in 3.6.

apparently now pyenv is recommended. I've luckily used it in the past, but set up time is variable and sometimes not as straight forward, especially on a non-WSL Windows setup.

https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-venv

isagalaev,
@isagalaev@mastodon.social avatar

@erictleung your link says it's the other way around (and it is). python -m venv <dir> is indeed the standard low-level way of creating a venv using just Python itself. Many people use higher-level tools on top of that, but they all ultimately call into the built-in venv module.

erictleung,
@erictleung@mastodon.social avatar

@isagalaev ah good catch! should've reread it a couple more times. trying to catch up on all these updates after being away for a couple of years is hard.

good to know python3 -m venv still works!

jamescooke,
@jamescooke@fosstodon.org avatar

@isagalaev @erictleung

Not all venv tools call "-m venv" especially those that existed before that module was in the stdlib (at py3.3 I think).

For example, Virtualenv uses its default "builtin" creator and does not call "-m venv".

See https://virtualenv.pypa.io/en/latest/user_guide.html#creators and https://virtualenv.pypa.io/en/latest/cli_interface.html#section-creator

  • All
  • Subscribed
  • Moderated
  • Favorites
  • python
  • kavyap
  • thenastyranch
  • ethstaker
  • osvaldo12
  • mdbf
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • Youngstown
  • khanakhh
  • Durango
  • slotface
  • rosin
  • cubers
  • JUstTest
  • everett
  • cisconetworking
  • tacticalgear
  • ngwrru68w68
  • Leos
  • GTA5RPClips
  • normalnudes
  • modclub
  • tester
  • anitta
  • megavids
  • provamag3
  • lostlight
  • All magazines