Add a project setting to control if and where a project can be published

[J-M0]

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

I would like to propose that poetry have a project-level configuration option that would let you restrict which repositories a package gets published to or even prevent it from being published at all.

Rust's package manager cargo has a field in its Cargo.toml file that does just that. I think the behavior described here is exactly what poetry should adopt.

https://doc.rust-lang.org/cargo/reference/manifest.html#the-publish-field

I work on both public and private projects and this would be a nice addition for my peace of mind. I could make sure a private package doesn't accidentally get published to PyPI or even just prevent a package that is early in development from being published prematurely. It would also make publishing to private repositories easier as you would not need to specify the private repository with poetry publish -r.

[NickleDave]

The way to do this is to include it in the "classifiers" section

[tool.poetry]
# ...
classifiers = [
    "Topic :: Software Development :: Build Tools",
    "Topic :: Software Development :: Libraries :: Python Modules"
]

You want to add

        "Private :: Do not Upload"

for your private projects

[NickleDave]

AFAIK this is the "official Pythonic" way, see
pypa/packaging.python.org#643

[J-M0]

That's a good trick to know, thank you. I still think being able to specify a default repository to publish to would be useful and that enforcing not uploading a package would be better served at the tool level rather than having PyPI reject a package after upload.

[gh640]

This might be same as #1537 .

[skewty]

Is this supported now? Its been over a year with no comments / updates.

[imochoa]

Is this supported now? Its been over a year with no comments / updates.

I think this doesn't actually depend on poetry. It's specified by PyPI already:
https://pypi.org/classifiers/

So it should work, I guess

[finswimmer]

Duplicate of #1537

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.