The same as option 2, but instead of overriding the url field, just override the whole table with a blank table (that is, remove the url entirely). The same wanted behavior could be achieved by setting it to any other URL that doesn’t work. This explicitly overrides the default behavior, which I prefer to option 1, although setting the URL to an empty string is not particularly great. Raised errors should probably catch that the value is an empty string to provide better context. Thus you could simply set = '' and disable PyPI (or any repo) uploads. If the PyPI default could be stored inside the config, it could be looked up and overridden in config, by specifying a new URL. This means that poetry publish is different from poetry publish -repository pypi, where the latter will look up pypi in your registered repos. Other similar options might be to provide an allowed-repos = array or disallowed-repos = array, or both: Ĭurrently, the default is hardcoded here.

The field name publish is intuitive for the boolean case, but unintuitive for the array. An empty list publish= would likely do the same thing as false leading to documentation confusion and multiple ways to do the same thing, and annoying that the publish option may have multiple types. It forces repetition of allowable repo names (leading to possible errors) and implicitly overrides default behavior. This follows an established standard from another packaging tool which uses TOML, and is easy to understand and document, but has disadvantages.

Option 1: Borrow Rust Cargo’s manifest publishįrom Rust Cargo’s publish field as in the OP. I have written down a host of options, there may be others as well. I’d be happy to push out a PR for this with some agreement from core devs on API. The more important question here is the API / user experience.

Trove free codes repeatable