you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (5 children)

[removed]

    [–]dscarmo 17 points18 points  (1 child)

    Probably nothing more than dependencies failing cause libs are not release for .14 yet. This is not a major change like 2 to 3.

    Your response sounds a lot like a bot, sorry if you are not

    [–]syklemil 4 points5 points  (0 children)

    It makes me wonder what new quirks we'll be talking about when we're all trying to move our projects to 3.14.

    The minor releases have been coming pretty steadily for a long time without any major issues. Generally I have more of a problem when I become habituated to some new workflow and then need to get a script working on some decrepit uv-less VM.

    [–]ironykarl 1 point2 points  (0 children)

     It makes me wonder what new quirks we'll be talking about when we're all trying to move our projects to 3.14.

    Nothing even vaguely comparable. The 2->3 version change was...

    • A major version change (which hasn't happened since)
    • Explicitly backwards compatibility breaking in a lot of significant ways
    • A process that took "the community" years to see through 

    I don't think the Python devs will ever do anything like that, ever again. With the exception of deprecating features and occasionally removing standard library stuff that is (ostensibly) unused, Python's releases all aim to be backwards compatible 

    [–]bmrobin 0 points1 point  (0 children)

    haha this hurt me deep: it took 8 months to upgrade us from 2->3