Patch: Avoid deprecation warnings

[kbevers]

Patch supplied upstream [0] but the maintainer hasn't merged it and there
are signs of the project being abandoned. This is a temporary fix
until the future of the project is resolved.

[0] ktosiek/pytest-freezegun#36

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.

[conda-forge-linter]

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 (recipe) and found some lint.

Here's what I've got...

For recipe:

• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[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.

[kbevers]

@conda-forge-admin, please rerender

[duncanmmacleod]

Thanks for this, and apologies it took me so long to see it.

I presume that packaging should be added to requirements/run for this patch to work? Also marked a couple of typos. Thanks.

[kbevers]

Thanks for this, and apologies it took me so long to see it.

No worries. Thanks for getting to it now though.

I presume that packaging should be added to requirements/run for this patch to work?

packaging is part of the standard library so I wouldn't think so. Unless conda-forge does weird stuff to it's Python distribution...

[duncanmmacleod]

packaging is part of the standard library

I don't think that's right, at least I don't see it on https://docs.python.org/3/library/ and when I import it from my conda environment I get something in /site-packages/:

$ python3.10 -c "import packaging; print(packaging)"
<module 'packaging' from '/home/duncan/opt/mambaforge/envs/py310/lib/python3.10/site-packages/packaging/__init__.py'>

[kbevers]

Indeed you are correct. My bad. I've fixed it in the most recent commit.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing, but could not be merged (error=API error in POST to merge).

[kbevers]

Is the PR good or do you need more input from me?