Are pyproject.toml field requirements really compulsory?

[AndreGuerra123]

• 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.
• I have searched on public repositories to check if there was an alternative use.

Feature Request

As an app and api developer I usually don't use the isolation poetry excellently provides since I'm building and deploying in containers most of the time. However I'm using other features of the tool which I really appreciate, for instance install the packages provided in pyproject.toml, use the poetry lock, scripts and dependency structure. In my particular case I won't see the need to have some required fields used for packaging such as version, authors, and description. This for instance is not present at conda. I know that they are different goals between packaging a library and setting an app and I consider then to be both types of "projects" and my feature request is to allow that to be defined in the pyproject.toml somehow, or loosen the requirements on those fields. So far, I noticed in public available projects these fields are left on blank when deploying apps but I don't know the implications.

[finswimmer]

Hey @AndreGuerra123,

what you are asking for was already asked before in #1132

fin swimmer

[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.