[BUG] There should not be any direct_url.json file in Python packages.

[fabcor-maxiv]

Describe the bug
The created recipes do not take care of removing the direct_url.json file that ends up being created by pip during the build process.

To Reproduce
Let Grayskull create a recipe for a Python package (grayskull pypi PackageName) and build the package. The resulting package contains a direct_url.json file in site-packages/PackageName-1.2.3.dist-info.

Expected behavior
No direct_url.json file should be present in site-package/PackageName-1.2.3.dist-info (in the package nor once installed on disk).

Outputs
The recipe created looks like this:

build:                                                                          
  script: {{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation

It probably should look like this:

build:                                                                          
  script:
    - {{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation
    - find <site-packages-path> -delete -name direct_url.json

Environment

• grayskull --version
  • 2.5.3

Additional context
I am not too familiar with conda packaging ecosystem, so it might well be that I am misunderstanding a whole bunch of things.

The specification regarding direct_url.json is here: https://packaging.python.org/en/latest/specifications/direct-url/#direct-url

As far as I can tell, there really should not be any direct_url.json file in site-package/PackageName-123.dist-info when installing from repository. This file should be created only "when installing a distribution from a requirement specifying a direct URL reference (including a VCS URL)". I am not sure how well that translates into the conda side of things. But for sure it causes some incompatibilities.

I am honestly not sure what part of the process is at fault here. Is it the recipe creator, the package builder, or the conda installer? Maybe it would help if pip had an option flag to bypass the creation of this file, but as far as I can tell pip is not doing anything wrong, here.

Some references:

• pip freeze on a fresh Miniconda env returns certifi @ file:///opt/conda/conda-bld/certifi_1655968806487/work/certifi conda#11580 (comment)
• Poetry overwrites existing conda packages even if versions match python-poetry/poetry#6408