Installing _only_ scripts to a different location, modules and packages normally

[jackjansen]

What's the problem this feature will solve?

I have a Python package that consists of a number of extension modules and packages and a number of command line scripts. This Python package is part of a larger collection that also contains native executables, libraries, etc.

I am trying to install the modules and packages normally (for the Python I'm using) and the scripts into a bin directory where all my native executables also live.

Describe the solution you'd like

I'd like --install-option="--install-scripts=/usr/local/bin" to work again, possibly through an extended --I-know-what-i-am-doing option to enable it.

Alternative Solutions

Issue #3934 has a --target-scripts option that would do what I want.

Another possible option would be to use --target, if there was a way I could then instruct pip to add a .pth file pointing to my target directory into the "normal" site-packages.

Additional context

When creating a brew formula for the Mac I'm giving a dependency on the Python I need, and the Python modules and packages should be installed into that Python (so people can use my software from Python). The command-line scripts, however, should be installed into /usr/local/Cellar/mysoftware/... so they don't pollute the /usr/local/bin space unless the user has done a brew link.

On Windows there is a very similar situation: Most of my software is installed into C:\Program Files\mysoftware\bin and this is where my command line scripts should be too. But the Python packages need to go into the normal site-packages inside the Python installation otherwise people cannot use them.

Code of Conduct

• I agree to follow the PSF Code of Conduct.

[uranusjr]

I would say this is a special case of #4575, and instead of adding specific flags for everything, one flag allowing the user to supply a custom scheme should be introduced instead.

[jackjansen]

Interesting, I hadn't come across that issue....