Replies: 1 comment
-
I understand that attributes as author and version are not only for published packages, but a general attribution to a project. In given moment, a project had its version, maintainers, should know info (readme). And, speaking strictly about poetry, it define itself as Also, it's interesting to know that And, in the future versions. |
Beta Was this translation helpful? Give feedback.
-
I understand that a README file, the authors field, version, etc. are required for publishing a package.
But, what if I only want to use poetry for dependency management? It seems like a completely valid way to use poetry, but the enforcement of these fields makes it seem like it isn't. Other package managers such as NPM, Composer, etc. don't make the strict assumption that the user is publishing a package.
I'm currently working in a monorepo with several different AWS CDK stacks which all manage their own dependencies with poetry, but it seems pretty silly that each and every one of these must have a README, authors, etc...
Any reason why poetry is designed this way?
Beta Was this translation helpful? Give feedback.
All reactions