Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"private" packages
See original GitHub issue- I have searched the issues of this repo and believe that this is not a duplicate.
I think it would be useful if in my pyproject.toml I could specify that a package is private. This could be done via [tool.poetry] private = true. What this would do is disallow poetry publish without an explicit repository, to prevent accidental publishing to pypi.org. It could also make the license key optional. There may be other ways private projects should behave differently, but for now I’m mostly interested in the publish prevention.
If this is a feature that is desirable, I’d be happy to implement it. EDIT: See https://github.com/ojii/poetry/tree/private-packages for a simple implementation.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ojii That may be true, but then there’s the fact that you could be able to specify a default publish repository in the pyproject.toml, and be done with it, without using classifiers, or having to implement and use
private = true.I still think
private = truewould be a lot easier to understand and remember. With the classifier I’ll have to look it up every time. But I guess it works…