Eryk Sun <eryk...@gmail.com> added the comment:
> "C:\Users\chris\code\project\myenv\Scripts\python.exe"
Have you tried different case combinations for "Users" and "Scripts"?
* C:\users\chris\code\project\myenv\scripts\python.exe
* C:\users\chris\code\project\myenv\Scripts\python.exe
* C:\Users\chris\code\project\myenv\scripts\python.exe
* C:\Users\chris\code\project\myenv\Scripts\python.exe
> fsutil.exe file queryCaseSensitiveInfo C:\
Have you checked "C:\Users\chris\code\project\myenv"?
---
Off Topic
> Open Powershell (via both native Powershell app or the new
> Windows Terminal)
FYI, "native PowerShell app" is not the right way to think of this. Both cases
run the same command-line interface (CLI) shell (i.e. pwsh.exe or
powershell.exe), which is a console application that either inherits or
allocates a console session (i.e. an instance of conhost.exe or
openconsole.exe). When run from a graphical desktop application (e.g.
explorer.exe), a console application usually has to allocate a new console
session since there's none to inherit. Currently there's no way to set a
default terminal for console applications, so a regular console session is
allocated, which creates its own window. When run from a terminal in Windows 10
(e.g. Windows Terminal), a console application inherits a headless console
session (i.e. pseudoconsole mode), and the user interface is provided by the
terminal.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue41925>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
