Feedback on a Python interpreter discovery mechanism

[brettcannon]

I was wondering if there was any feedback from this project on brettcannon/python-launcher#168 as a tool-agnostic way to communicate what environments there are (and if there's a specific one people would be expected to use)? As a tool that both creates and uses virtual environments, I wanted to get your perspective on the proposal. I'm not specifically expecting any coding work, just whether this proposal makes sense to you.

[ofek]

Nice! So you're saying:

[project.scripts]
_py_launcher_hatch = "hatch.discovery:main"

right?

For shell stuff see:

• https://hatch.pypa.io/1.2/config/hatch/#shell
• https://github.com/pypa/hatch/blob/master/src/hatch/utils/shells.py

[brettcannon]

Nice! So you're saying:

[project.scripts]
_py_launcher_hatch = "hatch.discovery:main"

With hatch.discovery:main returning the expected JSON output for the environment you expect the user to use, that's exactly what I'm saying. 🙂

[ofek]

Cool, I guess I'll just always return the default environment.

[brettcannon]

It would probably depend on what's being asked of the tool making the call. Thinking from the Python Launcher, running py probably means whatever default is. But if people set up environments for different Python versions, then py -3.9 may be different than default if there's a Python 3.9 environment. This ties into brettcannon/python-launcher#168 (comment) where I discuss the idea of passing down whatever information is available.

The key point is it's up to you to make the decision of what you would think a Hatch user would want if there was no version restriction. You could return more than just default and let the caller decide based on whatever the newest Python version found is.

And listing all available environments is a separate thing.

[ofek]

Ah, I see. Count Hatch in 🙂