add label-studio

[moritzwilksch]

... and a bunch of its dependencies

this isn't quite there yet. The initial build yields:

Could not solve for environment specs
The following packages are incompatible
├─ django-cors-headers 3.6.0.*  does not exist (perhaps a typo or a missing channel);
├─ django-csp 3.7.*  does not exist (perhaps a typo or a missing channel);
├─ django-model-utils 4.1.1.*  does not exist (perhaps a typo or a missing channel);
├─ django-rq 2.5.1.*  does not exist (perhaps a typo or a missing channel);
├─ drf-dynamic-fields 0.3.0.*  does not exist (perhaps a typo or a missing channel);
├─ drf-flex-fields 0.9.5.*  does not exist (perhaps a typo or a missing channel);
├─ drf-generators 0.3.0.*  does not exist (perhaps a typo or a missing channel);
├─ humansignal-drf-yasg >=1.21.9  does not exist (perhaps a typo or a missing channel);
├─ label-studio-converter 0.0.58.*  does not exist (perhaps a typo or a missing channel);
├─ launchdarkly-server-sdk 8.2.1.*  does not exist (perhaps a typo or a missing channel);
├─ rq 1.10.1.*  does not exist (perhaps a typo or a missing channel);
├─ rules 2.2.*  does not exist (perhaps a typo or a missing channel);
└─ xmljson 0.2.0.*  does not exist (perhaps a typo or a missing channel).

Bumps

TBD: does this break everything?

• bump django-cors-headers >=3.6.0 (older version not on conda forge)
• bump django-model-utils >= 4.1.1 (4.1.1 version not on conda forge, 4.0.0 -> 4.3.1)
• bump drf-dynamic-fileds >= 0.3.0 (only version on conda forge is 0.4.0)
• bump drf-flex-fields >= 0.9.5 (older version not on conda forge, oldest one on CF is 1.0.0)
• bump drf-generators >= 0.3.0 (older version not on conda forge, oldest one on CF is 0.5.0)
• bump launchdarkly-server-sdk >= 8.2.1 (older version not on conda forge, oldest one on CF is 9.0.0)
• bump rq >= 1.10.1 (1.10.1 version not on conda forge, 1.9.0 -> 1.15.1)
• bump rules >= 2.2.* (older version not on conda forge, oldest one on CF is 3.3)
• bump xmljson >= 0.2.0 (older version not on conda forge, oldest one on CF is 0.2.1)
• bump redis-py >=3.5.0,<3.6.0 to >= 4.0.0 due to minimum requirements by rq

Blockers

• django-rq feedstock has not been updated for years, maintainers unresponsive
  • add maintainer: @conda-forge-admin, please add user @moritzwilksch django-rq-feedstock#13
• label-studio-convert doesn't build yet
• label-studio-converter is missing a LICENSE file (fix: Create LICENSE file HumanSignal/label-studio-converter#298)
• we should patch attr to be named dry_attr. We need https://pypi.org/project/attr/ which is shadowed by https://prefix.dev/channels/conda-forge/packages/attr

To Check

• humansignal-drf-yasg is a weird release of https://github.com/axnsan12/drf-yasg?

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-webservices]

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/attr/meta.yaml, recipes/django-csp/meta.yaml, recipes/humansignal-drf-yasg/meta.yaml, recipes/label-studio/meta.yaml, recipes/label-studio-converter/meta.yaml) and found some lint.

Here's what I've got...

For recipes/attr/meta.yaml:

• Feedstock with the same name exists in conda-forge.
• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipes/django-csp/meta.yaml:

• The home item is expected in the about section.
• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipes/humansignal-drf-yasg/meta.yaml:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

For recipes/label-studio-converter/meta.yaml:

• The license item is expected in the about section.

[conda-forge-webservices]

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/django-csp/meta.yaml, recipes/humansignal-drf-yasg/meta.yaml, recipes/label-studio/meta.yaml, recipes/label-studio-converter/meta.yaml) and found some lint.

Here's what I've got...

For recipes/humansignal-drf-yasg/meta.yaml:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

For recipes/label-studio-converter/meta.yaml:

• The license item is expected in the about section.

[moritzwilksch]

note: LS's dependencies are pinned quite strictly, sometimes to rather old versions

• Can't use LiteLLM for ML backend because of pinned jsonschema and jinja2 dependencies HumanSignal/label-studio#6105
• Relax dependencies for boto3, botocore and numpy (to start with) HumanSignal/label-studio#5000
• Relax dependencies or allow botocore==1.19.52 HumanSignal/label-studio#1998
• Loosen Pip Requirements HumanSignal/label-studio#557
• pip install of label-studio and label-studio-sdk can't be resolved HumanSignal/label-studio#3662