Automatically convert versioned dependencies from poetry.lock to Anaconda's meta.yaml

[amotl]

Comment:

Hi there,

coming from a suggestion by @xylar at https://github.com/conda-forge/wetterdienst-feedstock/pull/76/files#r1034481764, I am wondering whether there is no utility program already, which assists in creating/updating the requirements section in recipe/meta.yaml, using the poetry.lock file as input.

Of course, it should adhere to the semantics outlined by @xylar in detail. Thank you very much!

Note that ^1.3 in a pyproject.toml is equivalent to >=1.3,<2.0 here in the meta.yaml (which doesn't know about ^). But versions starting with 0. are a special case so ^0.8 is the same as >=0.8,<0.9, for example.

With kind regards,
Andreas.

[xylar]

There is a tool that does this from setup.py: https://github.com/conda-incubator/grayskull. Grayskull doesn't yet fully support pyproject.toml files, just setup.py but the PyPI version of wetterdienst has such a setup.py, it just doesn't look quite right.

I use grayskull to update the vast majority of the packages I maintain and I have a script for making that easy:
https://gist.github.com/xylar/13f003dc507f532bc065719d6e49be2f

I don't believe you would want to use poetry.lock. My understanding is that those dependencies are stricter than what is in the pyproject.toml and they wouldn't be appropriate for conda-forge.

[amotl]

Hi Xylar,

thanks for suggesting Grayskull ¹, this looks excellent. Let me also add pip-tools ², which fits into the same category of tools. Maybe both programs can be combined to create a pyproject.toml -> requirements.txt -> meta.yaml pipeline, or such?

With kind regards,
Andreas.

Footnotes

1. https://github.com/conda-incubator/grayskull ↩

2. https://github.com/jazzband/pip-tools ↩

[amotl]

Oh, here we go. -- python-poetry/poetry-plugin-export#159

[xylar]

Grayskull now fully supports pyproject.yaml. I think this problem is as solved as it can be on the conda-forge side. I don't see how poetry-plugin-export can help with conda-forge maintenance beyond what grayskull already does.

[amotl]

Excellent, thanks! Is it something we should add to an automated workflow now, or would it be a manual process to regularly convert pyproject.yml to the Conda specification file, using Grayskull?

[xylar]

I run a script with each update but I run it manually and I don't think we want to try to automate it because maintainer intervention is often required.

https://gist.github.com/xylar/13f003dc507f532bc065719d6e49be2f

[amotl]

Hi again,

I am closing this in favor of GH-103. Your support on this topic of Anaconda dependency management is true gold, @xylar. We hope you can irregularily keep up the spirit to continue supporting us here, like now where we are aiming to modernize a bit.

With kind regards,
Andreas.