`readme` is not required in pyproject.toml, but docs say it is
See original GitHub issueThe docs say that the readme
key is required:
readme
The readme file of the package. Required
The file can be either
README.rst
orREADME.md
.
but poetry check
works just fine without any mention of the readme in pyproject.toml.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
readme is not required in pyproject.toml, but docs say it is #237
The docs say that the readme key is required: readme The readme file of the package. Required The file can be either README.rst...
Read more >The pyproject.toml file | Documentation | Poetry
Poetry supports extras to allow expression of: optional dependencies, which enhance a package, but are not required; and; clusters of optional dependencies.
Read more >Configuring setuptools using pyproject.toml files
Starting with PEP 621, the Python community selected pyproject.toml as a standard way of specifying project metadata. Setuptools has adopted this standard ...
Read more >How to Create and Upload Your First Python Package to PyPI
A few weeks ago, I wanted to learn how to build my first Python package, and I was trying to figure out where...
Read more >Flit Documentation
New projects created with flit init now declare that they require flit_core >=2,<4 (PR #328). Any projects using pyproject.toml (not flit.ini) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should we close this since #242 got merged in? The “Closes #237” text on there didn’t trigger an automatic close here because
develop
is not the default branch.@sdispater - FWIW, I think it will be confusing to have people submit PRs against different branches depending on the type of change. If possible, I recommend having one branch to land incoming changes and making it the default branch. That will address issues like the one here.
poetry new
creates a newREADME.rst
but doesn’t add it to thepyproject.toml
. That could be changed as well, right? (I also think it should default to markdown, but that’s arguable)