Make noarch: python (ignore pypy)

[bollwyvl]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [x] 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)
• [x] Ensured the license file is being packaged.

[conda-forge-webservices[bot]]

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/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• In conda-forge.yml: $ = {'abi_migration_branches': ['4.x'], 'build_platform': {'linux_aarch64': 'linux_64', 'linux_ppc64le': 'linux_64', 'osx_arm64': 'osx_64'}, 'conda_build': {'pkg_format': '2'}, 'conda_forge_output_validation': True, 'github': {'branch_name': 'main', 'tooling_branch_name': 'main'}, 'provider': {'linux_aarch64': 'default', 'linux_ppc64le': 'default'}, 'test': 'native_and_emulated'}.

  Additional properties are not allowed ('abi_migration_branches' was unexpected)

  Schema

[bollwyvl]

@conda-forge-admin please rerender

[conda-forge-webservices[bot]]

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.

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/jupyter_core-feedstock/actions/runs/10985307266.

[bollwyvl]

@conda-forge/jupyter_core we could:

• go ahead and do this, effectively making this uninstallable with pypy on windowst going forward
• investigate some other way to have a pypy-only build
  • this will likely get harder to support in the future as conda-forge drops more pypy
• do nothing: wait for pywin32 to unblock the python312 migration, and deal with whatever it does

[minrk]

Can we do a noarch_platforms variant list like we do for ipykernel? But with variants:

• cpython
• pypy

and put runconstrained on `- python {{ implementation }}`?

Alternatively, we could have two variants, one with pywin32-on-windows dependency and one without, with the one without penalized by a feature or build offset. Effectively 'preferring' pywin32 on windows, but not requiring it.

[minrk]

Given the pypy transition, if this proves difficult, I think it's probably also okay to drop pypy here for new builds for now, and then try to get it back in a later build, if there's a need to keep things moving. LMK if you want a hand to try to get the variants built.