PackageInfo: Invalid constraint (PyYAML (>=5.1.*)) found in omegaconf-2.1.0 dependencies, skipping

[gygabyte017]

• 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: Windows 10
• Poetry version: 1.2.0a

Issue

In any project, the command:

poetry add omegaconf

leads to this error:

PackageInfo: Invalid constraint (PyYAML (>=5.1.*)) found in omegaconf-2.1.0 dependencies, skipping

so that the dependency pyyaml is not installed and therefore the package omegaconf will not work.

However with pip install omegaconf the package is installed correctly together with its dependency pyyaml. What may be wrong?

[finswimmer]

Hello @gygabyte017,

this was reported earlier in:

• Invalid PEP 440 version: '3.6.' #4201
• Version Parse error #4095

TL;DR: >=5.1.* is invalid and should be fixed by the maintainer of the package to >=5.1

fin swimmer

[HaukurPall]

Is there a workaround? I use Fairseq (https://github.com/facebookresearch/fairseq/) which depends on this broken omegaconf specification. This project is not released frequently and is heavily integrated into this version of omegaconf.

[MeWannaSleep]

@HaukurPall Hi, Have you find any workaround?

[HaukurPall]

@MeWannaSleep instead of using poetry I used pip :)

[SakarDev]

@MeWannaSleep instead of using poetry I used pip :)

But i already use pip and still getting same error!
pip install fairseq

[dimbleby]

you are using a closed issue on the poetry bug tracker to report an issue that you see when not using poetry. This is absurd.

I expect more recent pip is parsing version specifiers more accurately - and therefore now agrees with poetry that the invalid constraint is indeed invalid. Take your bug report to the project that provides the bad constraint.

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