Rebuild python310 0 1 h8682cc

[hmaarrfk]

Checklist

• [ ] Used a personal fork of the feedstock to propose changes
• [ ] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

[conda-forge-linter]

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

[k-dominik]

installing first doesn't help, I tried that already (tests are run from the build env)

I'm gladly proven wrong :) great that it works!

So installation did the trick?! I don't think https://github.com/conda-forge/vigra-feedstock/pull/85/commits/1fb0cc8b4b87414bb065c8114caa2ad69888e029 is necessary (also incomplete, that variable is checked more often in the same way)

[conda-forge-linter]

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-linter]

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

[hmaarrfk]

Ok, i removed the patch and trying again.

I think recent python 3.9 and 3.10 changed how they look for packages. They might not be looking in the current directory or something. Therefore the tests were failing there for windows. that is my hunch.

[hmaarrfk]

shall we merge this?

[jakirkham]

Thanks Mark! 😄