Randy Döring

Might be fixed in the main branch. 1.8.3: ``` $ poetry install --dry-run --all-extras | grep importlib-metadata - Installing importlib-metadata (8.2.0): Skipped for the following reason: Not required ``` main:...

I will try to take a closer look at the end of the week.

pre-commit.ci autofix

Trying out the examples, I unfortunately discovered some issues: 1. `tool.poetry.extras` will be deprecated in favor of `project.optional-dependencies` in the next version. I updated the examples to the new syntax...

Thanks for the update @reesehyde! I did not realize that the second example will work if I leave out the `extra != ...` in `project.optional-dependencies`. I updated the docs with...

> and some encoding warnings Can you tell me where I see these warnings? I thought it should be visible for example in the Ubuntu Python 3.13 pytest job when...

> Just one over-specified testcase that mysteriously is ever so slightly different on macos python 3.13. I assume we should just make the test more robust to allow any order...

@notpushkin @Secrus Am I missing something or has this been fixed by Warehouse? I can see a homepage link for both https://test.pypi.org/project/poetry-homepage-bug-repro/ and https://test.pypi.org/project/poetry-homepage-bug-workaround/

Might make sense. It should probably mentioned in https://python-poetry.org/docs/contributing#local-development ([source](https://github.com/python-poetry/poetry/blob/main/docs/contributing.md)) how to create a coverage report locally. In CI, the challenge is to create coverage reports for all Python versions...

> @radoering mentioned in discord that this might be related to poetry#9427 and `installer.re-resolve` but this is reported for `1.8.3` version You misunderstood. I said that #9427 (partially) fixes this...