New recipe with updated dependencies and maintainer

[thewchan]

Checking to see why pip check fails

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 @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[thewchan]

@conda-forge-admin, please rerender

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

[thewchan]

@hmaarrfk sorry for the ping; trying here but there's not a lot of feedback to debug why pip check is failing here...

[hmaarrfk]

does backporting uqfoundation/multiprocess#197 help

[thewchan]

@hmaarrfk we can try; using a patch?

[hmaarrfk]

yes, you can get the patch by going to the url and adding a .patch at the end

[thewchan]

yes, you can get the patch by going to the url and adding a .patch at the end

@hmaarrfk I didn't know this! I did this the long way this time but will note for future reference

[thewchan]

@conda-forge-admin, please rerender

[thewchan]

@hmaarrfk I don't think I got it to work?

[hmaarrfk]

No you did not get it to work.

It helps to run things in debug mode where you can see that the setup.cfg file uploaded to pypi.org is wrong.

I think that is what the patch tries to resolve.

Instead, I had to delete it:
#54

[thewchan]

got it, I can close this one in favor of yours if that helps

[hmaarrfk]

No. I explicitly said I don't want that in mine. You should take ownership

[thewchan]

@jschueller and @synapticarbors thanks to @hmaarrfk's help go this to work with pip check; this should alleviate many downstream woes (we hope anyway). Appreciate a review and merge 🙏