Vote to update to 3.11 or 3.12 - Ends June 23

[hmaarrfk]

Comment:

I don't think there is much to discuss.

We last updated to 3.10 about 2 years ago.

We should likely update again.

Let use emojis to vote.

Maintainer of miniforge very much encouraged.
Conda-forge core welcome.

Voting shall close June 23.

Use emojis to vote.

• 🚀 3.12
• 🎉 3.11
• 👀 3.10

[hmaarrfk]

For the larger community passerby's if you want your voice to be heard, it would be interesting to keep you distinct from the maintainers

Use emojis to vote.

• 🚀 3.12
• 🎉 3.11
• 👀 3.10

Please vote here, it may affect my one vote ;)

[hmaarrfk]

Core member votes:

• 3.11 -- @jakirkham @isuruf @jaimergp @mbargull
• 3.12 -- @hmaarrfk @jaimergp @ocefpaf @mbargull

Community vote: 3.12

[jakirkham]

@jaimergp did you mean to select both?

[hmaarrfk]

Well seems like a good old draw.

I'll leave it to the first person to press merge between:

• Update to python 3.12 #603
• Update to python 3.11 #604

[jaimergp]

Let's do Python 3.12 then :)

[jakirkham]

The main thing is to make sure all our tooling (like for bots and webservices) is available on Python 3.12

[mbargull]

Either version works for me (slight preference for 3.12).

• Pro for 3.11: More stable in terms of downstream support.
• Pro for 3.12: We have to update at some point to not get unnecessarily far behind again and 3.12 will be the expected baseline soon (since 3.13 is well into beta already).
  (I would've suggested we make sure to update not later than Q4 2024; now it's nearly start of Q3 -- not too far off...)

[hmaarrfk]

I've been "skipping odd versions" of python in my personal projects. Too much churn otherwise.

The pydantic hiccup did scare me though.... but I guess thats life.

[hmaarrfk]

Thank you all for your feedback. It seems that there is momentum behind the 3.12 update.

It may take an other week to get pushed since we want to synchronize it with a few other backward incompatibility changes