You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The direct_url.json file MUST be created in the *.dist-info directory by installers when installing a distribution from a requirement specifying a direct URL reference (including a VCS URL).
This file MUST NOT be created when installing a distribution from an other type of requirement (i.e. name plus version specifier).
The way I understand the specification, this is the second clause that should apply in the example I presented above, and there should not be any direct-url.json in the .dist-info directory.
I assume that this file is created by a pip install step of the Conda recipe. This file is then added (blindly) to the .conda package. And finally this file is copied (incorrectly) by Micromamba to the install location with the rest of the content of the .conda package.
I know that the PyPA specifications might not be necessarily in scope for the Conda ecosystem. Anyway here is a case where this causes real incompatibility issues: python-poetry/poetry#6408 (comment).
The text was updated successfully, but these errors were encountered:
As far as I understand, it seems to me like Mamba and Micromamba are not respecting the "Direct URL Origin" standard.
For example:
From my reading of the specification, this file should not exist.
Here is an excerpt of the specification:
The way I understand the specification, this is the second clause that should apply in the example I presented above, and there should not be any
direct-url.json
in the.dist-info
directory.I assume that this file is created by a
pip install
step of the Conda recipe. This file is then added (blindly) to the.conda
package. And finally this file is copied (incorrectly) by Micromamba to the install location with the rest of the content of the.conda
package.I know that the PyPA specifications might not be necessarily in scope for the Conda ecosystem. Anyway here is a case where this causes real incompatibility issues: python-poetry/poetry#6408 (comment).
The text was updated successfully, but these errors were encountered: