GitHub - conda-forge/conda-forge-metadata: programmatic access to conda-forge's metadata · GitHub
Skip to content

About

programmatic access to conda-forge's metadata

Resources

Contributing

Security policy

Stars

6 stars

Watchers

3 watching

Forks

Repository files navigation

conda-forge-metadata

tests pre-commit.ci status Publish to PyPI

programmatic access to conda-forge's metadata

Versioning and Deprecations

conda-forge-metadata follows CalVer using the YYYY.MM.DD scheme.

conda-forge-metadata's API is defined as the collection of all reachable symbols whose fully qualified import path does not feature a leading underscore in any of its components. The API covers renames and, if callable, changes in signatures (argument and keyword argument names and types, plus the return types). The API also covers the command-line interface. Any other symbol may change at any time and has no guaranteed API.

All API changes must undergo a 60-day deprecation period, must be clearly indicated via a DeprecationWarning.

About

programmatic access to conda-forge's metadata

Resources

Contributing

Security policy

Stars

6 stars

Watchers

3 watching

Forks

Releases

Used by

Contributors

Languages