Adding Resourcecode python package

[NRaillard]

This recipe has been prepared using greyskull , from pypi package 'resourcecode'.

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

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

For recipes/resourcecode/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the run section of the recipe, you should usually use the pin python >={{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

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

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[NRaillard]

@conda-forge/help-python, ready for review!

[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/resourcecode/meta.yaml) and found it was in an excellent condition.

[synapticarbors]

I noticed that in the upstream setup.py, it has python_requires=">=3.9, <3.13". If this package is going to break with python 3.14, then you should put an upper bound on python under run:

- python >={{ python_min }},<3.14

Otherwise this looks good.

[NRaillard]

thanks @synapticarbors, indeed AFAIK the package is not working on python from 3.13 for the moment, so I fixed the version on the recipe. Could it be changed after if we manage to soften this constraint ?