python / python/cpython

activate.ps1 in venv for Windows should encoded with BOM

Open
#80,790 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) 3.8 (EOL) OS-windows type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 36609
Nosy @pfmoore, @tjguk, @zware, @zooba

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2019-04-12.08:27:01.281>
labels = ['3.7', '3.8', 'OS-windows', 'type-crash']
title = 'activate.ps1 in venv for Windows should encoded with BOM'
updated_at = <Date 2019-04-12.18:06:53.148>
user = None

bugs.python.org fields:

activity = <Date 2019-04-12.18:06:53.148>
actor = 'steve.dower'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2019-04-12.08:27:01.281>
creator = '\xec\xa0\x95\xed\x95\x9c\xec\x86\x94'
dependencies = []
files = []
hgrepos = []
issue_num = 36609
keywords = []
message_count = 2.0
messages = ['340014', '340092']
nosy_count = 5.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', '\xec\xa0\x95\xed\x95\x9c\xec\x86\x94']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue36609'
versions = ['Python 3.7', 'Python 3.8']

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Windows venv generation path and the activate.ps1 template or output. Check how the script is encoded, then verify that generated Windows activation scripts include a BOM without changing other activation behavior. No test file is named in the issue, so use the existing venv or Windows test coverage you find nearby.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.