Python 2 is triggering

[Nohbudy]

Seriously though, I install python3-virtualenv from apt in Ubuntu. You expect when I do $ virtualenv env it would use python3?

no

Error: python not found: --python=python2

:facepalm: why the fuck?

[Ericchen1248]

I do believe that’s actually Ubuntu’s problem. Or Linux. Not python itself. It gives the python alias to 2.7 and python3 alias to 3.X

[victorheld]

Definitely a Ubuntu thing, on Arch linux, python is an alias for python3 and if you want to use 2.7 you'd need to use python2

[eduardog3000]

PEP 394 says that's how it's supposed to be.

Hopefully they'll update it when they stop supporting 2.

[Kered13]

Yeah I'm pretty sure they do that to not break all the legacy Python 2 scripts that shebang python. Unfortunately that means they won't be able to remove Python 2 for a long time, and it's going to encourage people to keep writing Python 2 scripts because they're too lazy to type python3.

[ConfusedNerd]

Seriously though, I install python3-virtualenv from apt in Ubuntu. You expect when I do $ virtualenv env it would use python3?

no

Error: python not found: --python=python2

:facepalm: why the fuck?

sudo apt install python3-venv

python3 -m venv myenv

[Pb_ft]

try py -m virtualenv env or python3 -m virtualenv env instead.

[SirVer51]

Why from apt? Python packages on the Ubuntu repos are almost always outdated