[issue32451] python -m venv activation issue when using cygwin on windows

Erik Bray added the comment: Coincidentally I just encountered this myself when trying to activate a venv created by Python for Windows while in a Cygwin shell. Indeed, bash for Cygwin is just like bash anywhere else, and considers it a syntax error to encounter unexpected CR's. Alas,

[issue32451] python -m venv activation issue when using cygwin on windows

Eryk Sun added the comment: > This is assuming that in all these cases people are installing Python > for Windows and trying to use it from a non-Windows shell (both WSL > and Cygwin have their own "native" Python builds that presumably > work). It should work from Cygwin and MSYS2 since

[issue32451] python -m venv activation issue when using cygwin on windows

Steve Dower added the comment: It probably just needs a gitattributes fix so it doesn't get converted when cloned to make the release build. This is assuming that in all these cases people are installing Python for Windows and trying to use it from a non-Windows shell (both WSL and Cygwin

[issue32451] python -m venv activation issue when using cygwin on windows

Eryk Sun added the comment: Why is the bash/zsh "activate" script getting distributed with CRLF line endings? Apparently Windows builds of bash (e.g. git-bash) can handle CRLF line endings, but Cygwin bash cannot. As to Linux bash in WSL, the activate script from a virtual environment

[issue32451] python -m venv activation issue when using cygwin on windows

Andrew Stanton added the comment: I dont think this is a Cygwin only problem, as this is happening to me when running WSL (Windows subsystem for Linux). I can run Scripts\Activate.ps1 from powershell, Scripts\activate.bat from cmd, but running scripts/activate from wsl reports this same

[issue32451] python -m venv activation issue when using cygwin on windows

R. David Murray added the comment: cygwin in not currently fully supported (there are people working on it, though). Can you determine if this is a bug in cygwin's bash support, or something else? It certainly works with bash shell on unix. I would presume that from

[issue32451] python -m venv activation issue when using cygwin on windows

New submission from Kevin : attempts from within cygwin: 1. The Posix way: $ python -m venv taco $ cd taco $ source bin/activate -bash: $'\r': command not found -bash: Scripts/activate: line 4: syntax error near unexpected token `$'{\r'' 'bash: Scripts/activate: line 4: