Unidecode error while exporting in Poetry 1.2

[nbro10]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: macOS Monterey (version 2.4)
• Poetry version: 1.2.0
• Link of a Gist with the contents of your pyproject.toml file: gist

Issue

I am getting a Unidecode error. Here's how to reproduce it.

1. Create a pyproject.toml as follows

[tool.poetry]
name = "poetry-unidecode-issue"
version = "0.1.0"
description = ""
authors = ["me"]
readme = "README.md"
packages = [{include = "poetry_unidecode_issue"}]

[tool.poetry.dependencies]
python = "^3.8"

python-slugify = {version = "^6.1.2", extras = ["Unidecode"]}

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

2. Do poetry update
3. Do poetry export -f requirements.txt --without-hashes --output requirements.txt and get the very useful 'Unidecode' error message. If you use the debug mode, you will also get a KeyError.

Solution

Change python-slugify = {version = "^6.1.2", extras = ["Unidecode"]} to python-slugify = {version = "^6.1.2", extras = ["unidecode"]}. So, clearly, Poetry searches for an extra dep, but it's case sensitive.

[dimbleby]

duplicate python-poetry/poetry-plugin-export#107

[nbro10]

@dimbleby This error does not occur in Poetry 1.1.15. In other words, if we have python-slugify = {version = "^6.1.2", extras = ["Unidecode"]}, and do an export, the error does not occur. Moreover, you can both do pip install Unidecode and pip install unidecode, so why isn't poetry also able to solve this issue? So, I am not sure this is really a duplicate.

[dimbleby]

nevertheless, it really is

[nbro10]

@dimbleby Ok, as you wish, but this is a poetry bug. Poetry should be able to map unidecode to Unidecode because they are the same dep.

[dimbleby]

if you separately want to raise an issue about the case-sensitivity of extras - well that will duplicate #6321 so we don't need that either!

[nbro10]

Ok, I agree that this is a duplicate of #6321, so I will close this.

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