Skip to content

If using an external Python, the bin directory might not be in PATH #32662

@mdorier

Description

@mdorier

Steps to reproduce

If you install a python package, the resulting files will be located in <prefix>/local instead of <prefix>. While this doesn't seem to be a problem for importing the module, it is a problem when the python package installs executables in bin. These executables end up in <prefix>/local/bin, which in not in PATH when loading the package or when in an environment that contains the package.

To reproduce, simply try installing a python package that has executables (e.g. py-flake8), then try to use said executable.

Error message

No response

Information on your system

  • Spack: 0.19.0.dev0 (123354e)
  • Python: 3.10.4
  • Platform: linux-ubuntu22.04-sandybridge
  • Concretizer: clingo

General information

  • I have run spack debug report and reported the version of Spack/Python/Platform
  • I have searched the issues of this repo and believe this is not a duplicate
  • I have run the failing commands in debug mode and reported the output

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions