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

[Steve Dower]

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 
modified file.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.8 -Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[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.

So I think activate.ps1 should be encoded as UTF8-BOM.

https://stackoverflow.com/questions/14482253/utf8-script-in-powershell-outputs-incorrect-characters

--
messages: 340014
nosy: 정한솔
priority: normal
severity: normal
status: open
title: activate.ps1 in venv for Windows should encoded with BOM
type: crash
versions: Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com