Skip to content

Vote to update to 3.11 or 3.12 - Ends June 23 #598

Closed

Description

@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

Activity

  1. locked as too heated and limited conversation to collaborators on Jun 5, 2024
  2. unlocked this conversation on Jun 5, 2024
  3. locked as too heated and limited conversation to collaborators on Jun 5, 2024
  4. unlocked this conversation on Jun 5, 2024
  5. changed the title [-]Vote to update to 3.11 or 3.12[/-] [+]Vote to update to 3.11 or 3.12 - Ends June 23[/+] on Jun 5, 2024
  6. pinned this issue on Jun 5, 2024
  7. hmaarrfk commented on Jun 5, 2024

    @hmaarrfk
    ContributorAuthor

    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 ;)

  8. hmaarrfk commented on Jun 22, 2024

    @hmaarrfk
    ContributorAuthor

    Core member votes:

    Community vote: 3.12

  9. jakirkham commented on Jun 22, 2024

    @jakirkham
    Member

    @jaimergp did you mean to select both?

  10. hmaarrfk commented on Jun 23, 2024

    @hmaarrfk
    ContributorAuthor

    Well seems like a good old draw.

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

  11. jaimergp commented on Jun 23, 2024

    @jaimergp
    Member

    Let's do Python 3.12 then :)

  12. jakirkham commented on Jun 23, 2024

    @jakirkham
    Member

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

  13. mbargull commented on Jun 23, 2024

    @mbargull
    Member

    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...)
  14. hmaarrfk commented on Jun 23, 2024

    @hmaarrfk
    ContributorAuthor

    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.

  15. hmaarrfk commented on Jun 25, 2024

    @hmaarrfk
    ContributorAuthor

    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

  16. unpinned this issue on Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions