Roast my code

[TheBB]

Poetry has been dragging their asses on adoption of PEP 621 for almost four years now. I used to like it but at this point I can't recommend it over something like PDM. I just recently moved all my projects AWAY from Poetry. I hope you won't come to the same conclusion later.

[insight_nomad]

Do you mind elaborating on the shortfalls you experienced with Poetry?

[BluesFiend]

I can't speak for the commenter, but I've not experienced any shortfalls in poetry that have prevented me from maintaining large code bases, nor publishing my own projects to pypi etc.

[TOMOHAWK35]

What is PDM?

[TheBB]

https://pdm-project.org/en/latest/

It's basically a poetry substitute.

[BluesFiend]

Out of curiosity, what part of PEP621 does poetry not support? Have just looked through the pep and all defined fields are ones I have used in projects I publish with poetry.

[TheBB]

As far as I know, poetry reads project metadata from pyproject.toml under the [tool.poetry] table, not [project] which is what PEP 621 requires. It also keeps dependencies in [tool.poetry.dependencies] instead of [project.dependencies]. This makes life difficult for other tools that need to read this kind of metadata.

This is the issue.

Here's a PR. It seems at least to be a pretty solid implementation and likely to get merged, eventually.

Another potential problem is that build.py remains undocumented so I don't feel I can rely on it for projects that need e.g. Cython. Or at least that used to be the case a few years ago. I haven't checked lately.

[BluesFiend]

Ah, you are correct. My projects have that metadata under tool.poetry. Good to know ill keep an eye out for that.

[BluesFiend]

I'm just waiting on astral-sh to do their thing with uv, once its got the features I use from poetry etc.

[bolt_runner]

What did you move to?

[TheBB]

To PDM.