[issue36609] activate.ps1 in venv for Windows should encoded with BOM

Steve Dower added the comment: Seems reasonable. The most reliable way to do this will be to override the copy function for this file in venv and write it out with "utf-8-sig" encoding. There are many ways that git will break things like this, so I wouldn't trust it to simply accept a

[issue36609] activate.ps1 in venv for Windows should encoded with BOM

Change by Karthikeyan Singaravelan : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware versions: +Python 3.8 -Python 3.6 ___ Python tracker ___

[issue36609] activate.ps1 in venv for Windows should encoded with BOM

New submission from 정한솔 : "activate.ps1" (venv) is currently encoded as UTF8 without BOM. But this cause an error if path of an environment contains non-ASCII characters. It seems Powershell can't recognize UTF8 without BOM. If I changed encoding of activate.ps1 to UTF8-BOM, it works well.