β² 32 βΌ Python 3.14.0 alpha 1 (discuss.python.org) submitted 2 years ago by norambna@programming.dev [M] to c/python@programming.dev 11 comments fedilink hide all child comments
[β] SatouKazuma@programming.dev 9 points 2 years ago (3 children) When's Pi-thon supposed to release? Next year? 2026? permalink fedilink source hideshow 6 child comments replies: [β] vzq@lemmy.world 8 points 2 years ago (2 children) Next year. Itβs a yearly release cadence. Also, 3.14 will be the last one in this version numbering scheme. The one after that will be 3.26. permalink fedilink source parent hideshow 4 child comments replies: [β] lime@feddit.nu 4 points 2 years ago (1 child) wait hang on, what? source on that? permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago (2 children) https://peps.python.org/pep-2026/ permalink fedilink source parent hideshow 4 child comments replies: [β] lime@feddit.nu 3 points 2 years ago oh no... permalink fedilink source parent [β] NostraDavid@programming.dev 3 points 2 years ago (1 child) It's still a draft, but that's just a weirdly unnecessary change, IMO. There is no need from anyone to have the versions shift by 11 versions. permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up. There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon. permalink fedilink source parent [β] SatouKazuma@programming.dev 3 points 2 years ago That's such a stupid change. TIL, though. Thanks for the heads up! permalink fedilink source parent [β] norambna@programming.dev [S] 6 points 2 years ago (1 child) Python 3.14 Release Schedule: https://peps.python.org/pep-0745/ 3.14.0 final: Wednesday, 2025-10-01 permalink fedilink source parent hideshow 2 child comments replies: [β] NostraDavid@programming.dev 1 point 2 years ago Here's a better overiew: https://devguide.python.org/versions/ permalink fedilink source parent [β] Midnitte@beehaw.org 4 points 2 years ago Aside from the other comment, just a heads up that Python switched to yearly releases 3.13 was released Oct 24, 3.12 was released Oct 23, so Oct 25 makes sense for 3.14 Maybe someday they'll switch to calendar versioning ;p permalink fedilink source parent
[β] vzq@lemmy.world 8 points 2 years ago (2 children) Next year. Itβs a yearly release cadence. Also, 3.14 will be the last one in this version numbering scheme. The one after that will be 3.26. permalink fedilink source parent hideshow 4 child comments replies: [β] lime@feddit.nu 4 points 2 years ago (1 child) wait hang on, what? source on that? permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago (2 children) https://peps.python.org/pep-2026/ permalink fedilink source parent hideshow 4 child comments replies: [β] lime@feddit.nu 3 points 2 years ago oh no... permalink fedilink source parent [β] NostraDavid@programming.dev 3 points 2 years ago (1 child) It's still a draft, but that's just a weirdly unnecessary change, IMO. There is no need from anyone to have the versions shift by 11 versions. permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up. There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon. permalink fedilink source parent [β] SatouKazuma@programming.dev 3 points 2 years ago That's such a stupid change. TIL, though. Thanks for the heads up! permalink fedilink source parent
[β] lime@feddit.nu 4 points 2 years ago (1 child) wait hang on, what? source on that? permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago (2 children) https://peps.python.org/pep-2026/ permalink fedilink source parent hideshow 4 child comments replies: [β] lime@feddit.nu 3 points 2 years ago oh no... permalink fedilink source parent [β] NostraDavid@programming.dev 3 points 2 years ago (1 child) It's still a draft, but that's just a weirdly unnecessary change, IMO. There is no need from anyone to have the versions shift by 11 versions. permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up. There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon. permalink fedilink source parent
[β] vzq@lemmy.world 3 points 2 years ago (2 children) https://peps.python.org/pep-2026/ permalink fedilink source parent hideshow 4 child comments replies: [β] lime@feddit.nu 3 points 2 years ago oh no... permalink fedilink source parent [β] NostraDavid@programming.dev 3 points 2 years ago (1 child) It's still a draft, but that's just a weirdly unnecessary change, IMO. There is no need from anyone to have the versions shift by 11 versions. permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up. There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon. permalink fedilink source parent
[β] NostraDavid@programming.dev 3 points 2 years ago (1 child) It's still a draft, but that's just a weirdly unnecessary change, IMO. There is no need from anyone to have the versions shift by 11 versions. permalink fedilink source parent hideshow 2 child comments replies: [β] vzq@lemmy.world 3 points 2 years ago The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up. There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon. permalink fedilink source parent
[β] vzq@lemmy.world 3 points 2 years ago The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up. There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon. permalink fedilink source parent
[β] SatouKazuma@programming.dev 3 points 2 years ago That's such a stupid change. TIL, though. Thanks for the heads up! permalink fedilink source parent
[β] norambna@programming.dev [S] 6 points 2 years ago (1 child) Python 3.14 Release Schedule: https://peps.python.org/pep-0745/ 3.14.0 final: Wednesday, 2025-10-01 permalink fedilink source parent hideshow 2 child comments replies: [β] NostraDavid@programming.dev 1 point 2 years ago Here's a better overiew: https://devguide.python.org/versions/ permalink fedilink source parent
[β] NostraDavid@programming.dev 1 point 2 years ago Here's a better overiew: https://devguide.python.org/versions/ permalink fedilink source parent
[β] Midnitte@beehaw.org 4 points 2 years ago Aside from the other comment, just a heads up that Python switched to yearly releases 3.13 was released Oct 24, 3.12 was released Oct 23, so Oct 25 makes sense for 3.14 Maybe someday they'll switch to calendar versioning ;p permalink fedilink source parent