File extension for scripts on windows is unclear

[maltekliemann]

BPO	44427
Nosy	@maltekliemann

^{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 2021-06-15.12:46:03.128>
labels = ['type-feature', '3.9', 'docs']
title = 'File extension for scripts on windows is unclear'
updated_at = <Date 2021-06-15.12:46:03.128>
user = 'https://github.com/maltekliemann'

bugs.python.org fields:

activity = <Date 2021-06-15.12:46:03.128>
actor = 'maltekliemann'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-06-15.12:46:03.128>
creator = 'maltekliemann'
dependencies = []
files = []
hgrepos = []
issue_num = 44427
keywords = []
message_count = 1.0
messages = ['395875']
nosy_count = 2.0
nosy_names = ['docs@python', 'maltekliemann']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44427'
versions = ['Python 3.9']

[maltekliemann]

It is common practice to use no extension for python scripts on UNIX. In 3.8.1.4., it is hinted that a script with a shebang line can be executed on windows only if the file extension of the script is associated with the python launcher.

I'm not sure where the right place is, but I suggest clearly stating that this is a critical requirement. As scripts on UNIX usually don't use file extensions, using these scripts without further modification is not possible cross-platform.