#15481 Exposing package metadata like entrypoints when running tests Issue created by achimnol Is your feature request related to a problem? Please describe. Currently pex and pants does not allow making editable installation of source packages. I'd like to have a way to expose the package metadata (particularly, the entry points read via

importlib.metadata.entry_points()

) in the pex environment for pytest (

./pants test ...

) somehow. Describe the solution you'd like • Having an option to make editable installations of designated

python_distribution()

targets inside the pex environment for pytest • Having an option to copy BUILD files into the pex environment for pytest • Better ideas? Describe alternatives you've considered I've written a custom BUILD file parser that scans and extracts entrypoint mappings from sibling directories and all subdirectories of the "{buildroot}/src" directory. This workaround works well when using the exported venv to run Python codes directly. However, this method does not work because there is no BUILD files nor package metadata inside the pex environment for pytest. Additional context I'm working on a Python project that enumerates and loads its own (plugin) modules using

importlib.metadata.entry_points()

. pantsbuild/pants