Adding new pyplaces version

[tbanken]

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.

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

• recipes/pyplaces/meta.yaml:
  • lints:
    • Feedstock with the same name exists in conda-forge.

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

[tbanken]

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

[ocefpaf]

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

This is a duplicate package, no? If you need to update it you have to do in the feedstock.

[tbanken]

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

This is a duplicate package, no? If you need to update it you have to do in the feedstock.

yes, i didn't realize what the workflow was but the bot pointed me to the feedstock. thanks for the followup!