[issue41626] port shebang of tools from python2 to python3

Christian Heimes added the comment: make_ssl_data.py is an internal tool that generates internal header files. It's rarely used. The tool is not bound to any Python version, too. Feel free to change the shebang or leave it as it is. I don't care. --

[issue41626] port shebang of tools from python2 to python3

Change by hai shi : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41626] port shebang of tools from python2 to python3

hai shi added the comment: I create PR23581 to remove the inner Tools' shebang. But I am not remove Tools/ssl/make_ssl_data.py, Tools/gdb/libpython.py in PR23581. * To make_ssl_data.py, I guess Christian may give us some guide. * libpython.py will be installed in kinds of OS, some OS will

[issue41626] port shebang of tools from python2 to python3

Change by hai shi : -- pull_requests: +22459 pull_request: https://github.com/python/cpython/pull/23581 ___ Python tracker ___ ___

[issue41626] port shebang of tools from python2 to python3

hai shi added the comment: typo error: PR21913->PR21931 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41626] port shebang of tools from python2 to python3

hai shi added the comment: Sorry for my delay~ >I think some of these work with any Python, but some need the locally built >interpreter to give correct results. >It could avoid confusion and mistakes to remove the shebangs and executable >bits from the scripts that need a local Python, and

[issue41626] port shebang of tools from python2 to python3

Terry J. Reedy added the comment: Thoughts I wrote on the PR that belong here. (Thanks for the reminder, Éric.): *The use of #! in both stdlib and tools seems rather inconsistent. * Stdlib modules are best run with -m mod so as to run the code with the exact python binary they are meant

[issue41626] port shebang of tools from python2 to python3

Change by Ned Deily : -- Removed message: https://bugs.python.org/msg379245 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue41626] port shebang of tools from python2 to python3

Ned Deily added the comment: To address some of the concerns: - The shebang line in Mac/BuildScript/build-installer.py can be safely removed. - "Lib/idlelib/pyshell.py for example, maybe the IDLE entry point is just a symlink to that file" It's not, at least for unix-y builds. In

[issue41626] port shebang of tools from python2 to python3

Ned Deily added the comment: To address some of the concerns: - The shebang line in Mac/BuildScript/build-installer.py can be safely removed. - "Lib/idlelib/pyshell.py for example, maybe the IDLE entry point is just a symlink to that file" It's not, at least for unix-y builds. In

[issue41626] port shebang of tools from python2 to python3

Éric Araujo added the comment: This is a minor thing, and not a particularly visible bug, but it could create confusion about how to run scripts so could be fixed. 1) For stdlib modules, I think the intended usage is `python3 -m encodings.rot_13`; I don’t expect anyone to run `python3

[issue41626] port shebang of tools from python2 to python3

Change by hai shi : -- keywords: +patch pull_requests: +21058 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21948 ___ Python tracker ___

[issue41626] port shebang of tools from python2 to python3

New submission from hai shi : After the EOL of python2, the shebang of tools should be ported from python2 to python3. some files like: https://github.com/python/cpython/blob/master/Objects/typeslots.py#L1 -- messages: 375855 nosy: shihai1991 priority: normal severity: normal