[issue42863] Python venv inconsistent folder structure on windows

Steve Dower added the comment: Considering you've just been encountering issues with mismatched case, you're likely aware of how much harder that will make it to fix. First you'll need a proposal on how to ensure deprecation warnings reach those who need them. I'd suggest for "Scripts"->"bin

[issue42863] Python venv inconsistent folder structure on windows

Darrel O'Pry added the comment: steve, I would be willing to champion this change. The process seems pretty straightforward. Create a release that creates the consistent layout on windows, symlinks the legacy paths, and adds some deprecation warnings. Then in a later release remove the sym

[issue42863] Python venv inconsistent folder structure on windows

Jeff Moguillansky added the comment: Thanks for the feedback, I understand -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue42863] Python venv inconsistent folder structure on windows

Paul Moore added the comment: Many tools hard code the "if windows then 'Scripts' else 'bin'" logic. They will simply fail to work with environments that don't have that layout. Yes, they probably should use sysconfig, but many don't (and sometimes for arguably good reasons, for example tool

[issue42863] Python venv inconsistent folder structure on windows

Jeff Moguillansky added the comment: Maybe we can consider adding additional params and a new code path to python -m venv? This way we don't break any existing functionality? e.g. -includedir=... -libdir=... -bindir=... ? -- ___ Python tracker <

[issue42863] Python venv inconsistent folder structure on windows

Steve Dower added the comment: > From the perspective of the overall system, I think it would simplify > integration and reduce complexity if we normalize folder structures across > platforms instead of having different folder structures. I agree. But from the perspective of not breaking eve

[issue42863] Python venv inconsistent folder structure on windows

Jeff Moguillansky added the comment: To give more context regarding this issue: I'm currently using meson build system to generate the pkg-config files, and it seems that the paths "include", "lib" are hardcoded. >From the perspective of the overall system, I think it would simplify >integ

[issue42863] Python venv inconsistent folder structure on windows

Steve Dower added the comment: I'm afraid not, at least not without breaking everyone who has hardcoded the paths already. And I'm pretty sure that include directory is never used anymore, either (at least not by distutils, and not by default). The sysconfig module provides the programmatic

[issue42863] Python venv inconsistent folder structure on windows

New submission from Jeff Moguillansky : When creating a virtual environment on windows using venv, the folder structure: "Scripts", "Include", "Lib", is inconsistent with other platforms (e.g. "include", "lib", "bin", etc). This causes various integration issues. For example, suppose we