[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: > This *should* reside in the bin directory That's your opinion, but there are other views. As Paul Moore said in this comment: https://github.com/python/cpython/pull/18083#issuecomment-577278587 Having things in bin *and* Scripts is more confusing than "on

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Erik Aronesty added the comment: > The Scripts/bin thing is not specific to venv - for whatever reason, the > original Windows implementation chose to use "Scripts" rather than "bin" That's irrelevant to the PR, which solves the problem in a compatible way. There's no compatibility

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: The Scripts/bin thing is not specific to venv - for whatever reason, the original Windows implementation chose to use "Scripts" rather than "bin" for the executables directory under Windows, and I don't think it can be changed now without affecting backward

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Erik Aronesty added the comment: See https://github.com/python/cpython/pull/18083 for an example of a 'simple copy' for shell script compatibility ... rather than trying to make Scripts move around (which it can't trivially). -- ___ Python

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Change by Erik Aronesty : -- pull_requests: +17474 pull_request: https://github.com/python/cpython/pull/18083 ___ Python tracker ___

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Erik Aronesty added the comment: the single Scripts/activate tool should be simply copied to bin/activate ... this is what you have to do to write a bash script for python now: source bin/activate || source Scripts/activate we should not assume that all windows users use things like CMD and

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Brett Cannon added the comment: > Are you proposing to bring that functionality, which these third-party tools > perform currently, into the stdlib? I was hoping to, but it turns out you can't make this work under Windows without inspecting the parent process (PowerShell and Command Prompt

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: > You can't. Tools like `pipenv shell` and `conda shell` end up with a new > shell running instead of changing the current shell in-place. Indeed. I raised it because of what you said earlier: > and so maybe proposing a simple `venv --activate ` that does

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Brett Cannon added the comment: > If venv is run in a child process of the shell, how does it set those > variables in the parent shell? You can't. Tools like `pipenv shell` and `conda shell` end up with a new shell running instead of changing the current shell in-place. --

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: > so maybe proposing a simple `venv --activate ` that does nothing more > than set those key environment variables If venv is run in a child process of the shell, how does it set those variables in the parent shell? I thought that wasn't possible (on POSIX,

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Brett Cannon added the comment: > Surely "on native Windows you run venv-path\Scripts\activate[.ps1], on POSIX > you use source venv-path/bin/activate" isn't *that* hard for new users to > grok, and would cover the vast majority of users? Sure, but how many times do we need to make people

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: > I think Brett is thinking about eliminating the manual activate part > entirely, but any tool trying to automate that needs to do a lot of > platform-specific checks. If you have more than one venv then it seems like some manual step is required to switch

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Tzu-ping Chung added the comment: > Surely "on native Windows you run venv-path\Scripts\activate[.ps1], on POSIX > you use source venv-path/bin/activate" isn't *that* hard for new users to > grok [...]? The if-Windows-X-else-Y part isn’t that hard; it’s the activate part that is :p I think

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: > Basically activation is the biggest stumbling block I find with new users Surely "on native Windows you run venv-path\Scripts\activate[.ps1], on POSIX you use source venv-path/bin/activate" isn't *that* hard for new users to grok, and would cover the vast

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Brett Cannon added the comment: I've personally never come across Scripts in any other situation than virtual environments, but that isn't saying much about my Windows exposure either. :) Basically activation is the biggest stumbling block I find with new users when it comes to trying to

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Tzu-ping Chung added the comment: There are more differences than Scripts/bin, like Windows use Lib but POSIX uses lib/pythonX.Y. IMO it’s probably better to stick with platform conventions, especially since those can be discovered with sysconfig.get_paths(expand=False). I wonder whether

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Vinay Sajip added the comment: The problem of bin over Scripts is that IIRC Scripts is baked-in in Windows, not just for venvs (e.g. a standard Python installation puts stuff in Scripts). So venv just sticks with the platform convention. -- ___

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Change by Brett Cannon : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Change by Brett Cannon : -- versions: +Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

DamlaAltun added the comment: I couldn't find a way to prevent being in seperate forms. When i add custom bin, custom include and custom libpaths 4 files are creating. The normal `bin`, normal `include` and custom `cbin` and custom `cinc`. You can unassign me. --

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

DamlaAltun added the comment: Working on that. -- nosy: +DamlaAltun ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

Change by Brett Cannon : -- assignee: -> brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35003] Provide an option to venv to put files in a bin/ directory on Windows

New submission from Brett Cannon : Having venv install files into Scripts/ on Windows but into bin/ on UNIX is troublesome for anything that tries to be cross-platform regarding virtual environments. Having a way to create a virtual environment on Windows where bin/ is used over Scripts/