Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieve packages from top_level.txt when possible #551

Merged
merged 2 commits into from
Aug 18, 2024

Conversation

beenje
Copy link
Contributor

@beenje beenje commented Aug 16, 2024

Description

The "packages" key that contains the list of modules part of the distribution is used in the test imports section of the conda recipe.
When "packages" isn't present, grayskull will use the name of the distribution, but that might differ.

packages isn't part of PKG-INFO metadata.
It can be retrieved from setup.py.
But when only pyproject.toml is present, this is usually not defined. Some info can be added but depends on the build backend.

For project using setuptools, packages can be retrieved from the top_level.txt file created in the .egg.info directory.

For other build backends, I don't have a solution.

The "packages" key that contains the list of modules part of the distribution
is used in the test imports section of the conda recipe.

It can be retrieved from setup.py.

When only pyproject.toml is present, this is usually not defined.
It can be added but depends on the build backend.

For project using setuptools, this information can be retrieved from the top_level.txt
file created in the .egg.info directory.

When "packages" isn't present, grayskull will use the name of the distribution,
but that might differ.
@marcelotrevisani marcelotrevisani merged commit 9ecb0a7 into conda:main Aug 18, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants