Randy Döring

This issue is solved in Poetry 2.0.1 so that there is no need for the workaround with deprecated fields anymore.

Missing extras should be irrelevant. See https://github.com/python-poetry/poetry-plugin-export/issues/326#issuecomment-2674997641. We should probably add a note in the readme that exported `requirements.txt` files should always be installed with `--no-deps`.

> We should probably add a note in the readme that exported `requirements.txt` files should always be installed with `--no-deps`. #331

Docs updated in #331.

So you are interested in #105 (`--all`)?

I also noticed that the tests sometimes fail in our CI, e.g. https://github.com/python-poetry/poetry/actions/runs/14800408919/job/41557614253?pr=10366. The re-run has always passed so far. @abn FYI

> Hmm. Is this isolated to Python 3.13? I have not paid attention to it yet. I will give an update as soon as I have observed some more failures.

The actual issue is python-poetry/poetry#707. If you install Poetry and the plugin via pipx (see https://python-poetry.org/docs/#installing-with-pipx and https://python-poetry.org/docs/plugins/#using-plugins), a suitable version of the plugin should be chosen.

> I wonder if we could make a repo in our org to store those examples instead of putting them here. @radoering what do you think? We could. Do you...

> [The docs](https://python-poetry.org/docs/repositories/#primary-package-sources) say that's perfectly fine and we've been using them for ages. Yes, it should be fine. (You can only have one default source, but default is deprecated...