Adding cvat-sdk python package

[achimgaedke]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/cvat-sdk/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/cvat-sdk/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12444332200. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/cvat-sdk/meta.yaml) and found some lint.

Here's what I've got...

For recipes/cvat-sdk/meta.yaml:

• ❌ noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

For recipes/cvat-sdk/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12446361931. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/cvat-sdk/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/cvat-sdk/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12468942456. Examine the logs at this URL for more detail.}

[achimgaedke]

Hey Maintainers!

@conda-forge/help-python ready for review, thank you!
I'm done with editing/fixing. Here's how far I got.

This recipe produces 3 outputs, cvat-sdk and two "extras" packages (-masks and -pytorch).

The windows test fails for cvat-sdk-pytorch, all other platforms succeed:

Could not solve for environment specs
The following packages are incompatible
\u251c\u2500 cvat-sdk-pytorch =2.24.0 pyhd8ed1ab_0 is not installable because it requires
\u2502 \u2514\u2500 pytorch =* , which does not exist (perhaps a missing channel);
\u251c\u2500 pytorch = * does not exist (perhaps a typo or a missing channel);
\u2514\u2500 torchvision =* * does not exist (perhaps a typo or a missing channel).

It depends on the broken pytorch providing package, which is not available due to the broken pytorch-cpu windows build - conda-forge/pytorch-cpu-feedstock#32

The cvat-sdk-pytorch noarch package for Windows is still useful in combination with the pytorch channel/gpu built provided by nvidia. I haven't managed to exclude windows from the tests without failing the linting stage.

This sounds to me like the exception mentioned in item 3 at https://conda-forge.org/docs/maintainer/guidelines/#generalities .

Any advice on this?

[ocefpaf]

Unless this uses pkg_resources, it is unlikely that it requires setuptools at runtime.

Suggested change

- setuptools >=21.0.0

[achimgaedke]

(Again grayskull generated) will remove it and see what happens.

[achimgaedke]

From the requirements list in the pip package. Now removed - pkg_resouces isn't used.

[ocefpaf]

?

[achimgaedke]

That's a yaml anchor for this section not to copy it below again. - Grayskull generated it.
https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/

If you like to have the sections written out I can replace those references by copying. Maybe that helps the conda recipe manager ?

[ocefpaf]

@marcelotrevisani when was this implemented in grayskull?

[achimgaedke]

grayskull pypi --maintainers achimgaedke --extras-require-all --extras-require-split cvat-sdk

with grayskull 2.7.3 - not sure since when this uses anchors.

[achimgaedke]

@conda-forge/help-python - Could you please review/consider this recipe for merging?

This recipe produces 3 outputs, cvat-sdk and two "extras" packages (-masks and -pytorch) - mimicking the pip package's extras.

The windows test fails for cvat-sdk-pytorch, all other platforms succeed:

    Could not solve for environment specs
    The following packages are incompatible
    \u251c\u2500 cvat-sdk-pytorch =2.24.0 pyhd8ed1ab_0 is not installable because it requires
    \u2502 \u2514\u2500 pytorch =* , which does not exist (perhaps a missing channel);
    \u251c\u2500 pytorch = * does not exist (perhaps a typo or a missing channel);
    \u2514\u2500 torchvision =* * does not exist (perhaps a typo or a missing channel).

It depends on the pytorch package, which is not available for windows due to the broken pytorch-cpu windows build - conda-forge/pytorch-cpu-feedstock#32

The cvat-sdk-pytorch noarch package for Windows is still useful in combination with the pytorch channel/gpu built provided by nvidia. I haven't managed to exclude windows from the tests without failing the linting stage.

This sounds to me like the exception made to failing pipelines mentioned in item 3 at https://conda-forge.org/docs/maintainer/guidelines/#generalities .

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!