Multiple Package indexes, Basic Authentication and pip.conf + .pypirc support

[HuM4NoiD]

• Does hatch include support for .pypirc and pip.[ini|conf]?
• Is it necessary to have /legacy/ at the end of the url to publish package to a private repository?
• Is there any other way except PIP_EXTRA_INDEX_URL/PIP_INDEX_URL variables to add simple package sources?
• Is there a way to use a particular index url for all projects created with hatch? (This is useful in situations where all projects are published/pulled from private pypi repository and this repository is excluded from source control)
• Authentication:
  • Do we have to specify basic auth like username:pass@host in the PIP_EXTRA_INDEX_URL/PIP_INDEX_URL for pulling packages?
  • Is there a seperate way to store basic auth credentials/token for pulling packages?
  • Are different credentials supported for different urls?

[maresb]

I'm wondering this too.

I noticed that PDM supports environment variable expansion for project.dependencies. As far as I can tell, this isn't standards-compliant, but it seems like a good practical compromise. I wonder if Hatch would be open to supporting this? Or should I write a plugin? 😄

[ofek]

We do, PDM copied it 😉

[maresb]

That's awesome. It took me a while to find the right place in the docs: Context formatting. I'm surprised that there is no link or examples from Dependency configuration.

It also seems a bit unfortunate that PDM didn't keep your syntax for interoperability, i.e. ${VAR} in PDM vs {env:VAR} in Hatch. But I suppose that's the problem when going outside of scope from standards.

Would it make sense to have dotenv support for context formatting? Something roughly like:

[tool.hatch]
context_formatting_dotenv = [".env.git-credentials"]