Open iamthebot opened 8 months ago
I agree this would be nice.
What you can currently do, is to generate a sdist
and then a recipe from that local archive:
cd /path/to/project
python -m build -s
grayskull pypi ./dist/*.tar.gz
We do that internally to create conda packages.
I agree this would be nice.
What you can currently do, is to generate a
sdist
and then a recipe from that local archive:cd /path/to/project python -m build -s grayskull pypi ./dist/*.tar.gz
We do that internally to create conda packages.
This comment is gold, it helped a lot, thanks! Maybe it's sufficient to get this approach into the documentation?
Is your feature request related to a problem? Please describe. Perhaps I'm missing something obvious but currently grayskull allows generating recipes for a pypi package (though it accepts a github URL) or a CRAN package.
It would be nice to be able to point it to a project available locally eg; using a PEP621 pyproject.toml setuptools project. This is especially useful when dual-releasing internal packages that may not be on a public github.
Describe the solution you'd like
grayskull local /path/to/pyproject.toml
generates a recipe given a pyproject.toml.Describe alternatives you've considered N/A
Additional context Add any other context or screenshots about the feature request here.