Disabling upload per-project

[cadojo]

For private package development, I've always been afraid of twine and similar tools' "by-default" behavior when it comes to publishing packages. I love the hatch version ... syntax, and the easy and fast builds and plugins, so I'd to have it as an option for in-house standard builds.

Is there any way to remove the default repository URL for hatch on a per-project basis? Something in pyproject.toml to specify the repository URL, so it isn't the public PyPi?

I know I can do so via the user config file, as described here, but I'd ideally like to specify this for every project, so someone would have to edit the config file or supply a command-line argument to upload to PyPi.

Is this supported?

[ofek]

Hey! You can do pypi/warehouse#5440

[project]
...
classifiers = [
    "Private :: Do Not Upload",
]

[cadojo]

Yes I have that too! I do think that still "sends bits" to pypi.org, no? And then PyPi sees the classifier, and rejects it?

I know that's splitting hairs, but if I'm correct about that logic, I'd ideally want something to prevent hatch upload from defaulting to pypi at all. Something like overloading the main and test names to my own, internal servers.

It seems like that specific case isn't supported, so if my Private :: classifier understanding is correct, would writing my own plugin be a good place to start? Could I overwrite upload in my own plugin, maybe?

[ofek]

fyi #342