Make sure you have checked all steps below.

Prerequisite

• Please consider implementing the feature as a hook script or plugin as a first step.
  • pyenv has some powerful support for plugins and hook scripts. Please refer to Authoring plugins for details and try to implement it as a plugin if possible.
• Please consider contributing the patch upstream to rbenv, since we have borrowed most of the code from that project.
  • We occasionally import the changes from rbenv. In general, you can expect changes made in rbenv will be imported to pyenv too, eventually.
  • Generally speaking, we prefer not to make changes in the core in order to keep compatibility with rbenv.
• My PR addresses the following pyenv issue (if any)
  • N/A

Description

• Here are some details about my PR

Scripts are generated based on a previous script -- because CPython scripts as of now have version-specific tweaks.

One-time manual editing will be required each time the necessary tweaks change. Presumably, CI failures will signal such moments.

It's then planned, with a separate PR, to

1. add a CI task to run this script to automatically support new CPython versions ASAP after a release and create a PR
2. add a CI task to automatically merge such PRs once CI checks pass
   More CI checks will likely be needed for these cases, likely running the full test suite.

Tests

• My PR adds the following unit tests (if any)
  N/A