[Request] Handle Python user base scripts directory

[bryanburke]

The Scoop manifest for Python (python.json) does not handle the Python user base scripts directory, so CLI scripts from packages installed in user mode (pip install --user) are not available on the PATH. Performing user installations of packages is considered best practice, and many packages (such as the popular Pipenv) recommend doing them.

Two possible solutions might be:

1. Construct the user base scripts directory and add it to PATH. The path can be constructed as follows: Join-Path -Path (Split-Path -Path (python -m site --user-site) -Parent) -ChildPath Scripts
2. Point the PYTHONUSERBASE environment variable to a directory within the Python install directory and persist it.

Related issue: ScoopInstaller/Versions#196

[TheRandomLabs]

A fix for this would be nice.

[Witchilich]

User scripts directory is actually (Split-Path -Parent (python -m site --user-site)) + "\Scripts"

[bryanburke]

@restia666ashdoll The Join-Path call above joins the path output by Split-Path -Path (python -m site --user-site) -Parent and Scripts. It handles the OS-specific path separator (\ on Windows) and is safer than string concatenation to build paths.

[dwettstein]

Installing Python using Scoop is already done on user-level (without --global flag) , so there is no need to additionally install packages using the --user flag.

If you still need to install packages on user-level and have them in the PATH, I suggest to create a PR. Paths are added to ENV using env_add_path.

env_add_path: Add this directory to the user's path (or system path if --global is used). The directory is relative to the install directory and must be inside the install directory.

Main/bucket/python.json

Line 84 in e4e85d9

"env_add_path": [

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rashil2000]

Closed by #2144