latest python version not listed on Pyenv for mac os

[Trid-collab]

I am using pyenv for installing python for wsl -Ubuntu on windows and macos. When I run pyenv install -l it shows the latest python version 3.12.3 whereas the same command on the latest version on mac os doesn't show that 3.12.3- its still at 3.12.2. How do it update that

[ViktorHaag]

It depends how you install pyenv on MacOS.

The PR to add support for 3.12.3 was merged three weeks ago, but has not yet been built into a release bundle (the latest release bundle currently is 2.4.0).

If you keep track of pyenv via installing via homebrew, for example, that 2.4.0 bundle is the latest one available.

Once this project rolls a new release that includes PR #2941, homebrew will eventually notice that new release and make it available. (See the notes in that PR for more information on this topic, and the workaround I suggest below.)

You might be able to get access to this more recent commit now by installing pyenv --HEAD with homebrew (which effectively means you're building this from source from the latest commit here) or you might want to keep the stability of just tracking releases as they are made and wait for the next release which will likely include support for 3.12.3.

[bulletmark]

Python 3.12.3 was released nearly a month ago but still not available in the latest release of pyenv. Many people use pyenv because they want the latest and greatest Python version before it is available on their distro. On Arch, stock Python is now 3.12.3 but the latest pyenv (v2.4.0) can give me is 3.12.2. Seems odd that no new pyenv release has been made.

[ViktorHaag]

I think it was just unfortunate timing. Reading the comments in PR #2941 suggests that pyenv has scheduled monthly releases, and the change to add support for 3.12.3 was added in immediately after a release was made, so that means waiting a month. In my view, waiting a month for a release is not an onerous burden; perhaps the maintainers could make it more clear what the release schedule is (in the docs perhaps?) so that expectations can be more clearly set.

But in my view, really it’s just a matter of being patient, or using the HEAD version of the code as commented as a workaround (and willing to take the risks that using a tip/dev version of a package entails).

[native-api]

We're currently collecting feedback on the desired release schedule at https://github.com/orgs/pyenv/discussions/2940

[Trid-collab]

I have a question ,are the release cycle for Linux and MacOS different. I find that 3.12.3 is already available through pynev in Ubuntu and I have already installed in my win 10 machine through wsl while on present on MacOS ye. Are the release cycles for both different. What’s the release cycle for Ubuntu. If that’s one faster cycle we could follow that or at max a 15 day after the release

…

On Fri, 3 May 2024 at 10:29 PM, native-api ***@***.***> wrote: We're currently collecting feedback on the desired release schedule at #2940 — Reply to this email directly, view it on GitHub <#2952 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOT3LVHRSWZAI56FA5T5EIDZAO66PAVCNFSM6AAAAABG6O2MN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGQYDCOJYHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>