Add deptry

[maresb]

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/deptry) and found some lint.

Here's what I've got...

For recipes/deptry:

• The home item is expected in the about section.
• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[conda-forge-webservices]

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/deptry) and found it was in an excellent condition.

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

For recipes/deptry:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-webservices]

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/deptry) and found it was in an excellent condition.

[maresb]

@conda-forge/help-python-c, ready for review of this Rust/Maturin recipe. (I hope this is the right team; it seemed the closest to Python/Rust.)

I seem to be hitting conda/conda-build#5122 when building on Windows, and it doesn't seem to me like there are currently any viable workarounds. Should I just disable Windows for now?

To be specific, during the build process this package depends on the ruff repository, and there are some huge filenames in there that Windows simply chokes on.

Caused by:
  failed to load source for dependency `ruff_python_ast`

Caused by:
  Unable to update https://github.com/astral-sh/ruff?tag=v0.3.4#5062572a

Caused by:
  path too long: 'C:/bld/deptry_1717936673004/_build_env/.cargo/git/checkouts/ruff-194cdb01f61cb8d9/5062572/crates/ruff_linter/src/rules/flake8_quotes/snapshots/ruff_linter__rules__flake8_quotes__tests__require_docstring_doubles_over_docstring_singles_mixed_quotes_class_var_1.py.snap'; class=Filesystem (30)

[fpgmaas]

GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.

I'm ok with this