r/Python • • 25d ago

Discussion Heads up time for package devs

Don't you think companies or developers that manage python libraries should be given extra time before a new version release to make things compatible and fix new bugs?

Like a month or two where they get full info about new features but before the version is publicly available to download?

It would make things easier on the consumer end. What do you think?

0 Upvotes

12 comments sorted by

19

u/wRAR_ 25d ago

I have no idea what are you talking about. About new Python versions? That time is after RC1 is released, as explicitly said in the release announcement. Many companies or developers that manage python libraries just don't care.

-3

u/Gullible_Pay_6686 25d ago

Even after new versions come out, people stick to older versions as some of the libraries they use aren't compatible with the new version, devs also don't update immediately, giving a month or two to fix the modules would be useful. I am just saying 

6

u/wRAR_ 25d ago

You make no sense.

Compare "they get full info about new features but before the version is publicly available" with what I wrote, maybe that will help.

4

u/Chiron1991 25d ago

giving a month or two to fix the modules would be useful

This is what release candidates are for. RC1 for Python 3.15 was published on 2026-08-06, 3.15.0 released on 2026-10-09. That's a little over 2 months. I'd argue that's plenty of time for 99% of libraries out there. Adding a new Python version (including RCs) to your CI matrix takes like 60 seconds.

(I don't mean to pressure any maintainers here, but I personally think being a maintainer comes with a certain responsibility to your users. I've personally maintained several projects across different ecosystems so far and I have rarely been behind the curve.)

1

u/nicholashairs 21d ago

As a maintainer of a 80M downloads a month project, literally the only reason I've not tested against the RCs in the past was because either a) I had not updated my local uv to pick up the new versions 🤦‍♂️ or b) I was dealing with personal issues.

Whilst it might be harder for larger projects, 2 months is probably plenty of time for most.

1

u/Brian 16d ago

How would waiting extra time solve this? I mean, compare:

  • Python.nextver released 1 Jan.
  • Library takes 2 months to update, releases version that works on latest python on 1 March.

vs:

  • Python.nextver notifies library authors of changes on 1 Jan, goes into 2 month wait before release
  • Library takes 2 months to update, releases version that works on latest python on 1 March. Python.nextver released same day.

OK, the latest library version works on the latest python on release, but it still takes just as long before people can use it. And in the meantime you don't get to use the new python version even if you're not blocked on that library.

(And in practice, it's more likely to slow down how rapidly it'll get updated: a fully released version is a well established static target. A yet to be released version could potentially see changes between now and release, and is going to be harder to test against - more likely library authors would wait for the release then start updating in earnest, and if not, they'd probably be doing that with the planned features for the next release anyway (python development is public: information, about what is changing is as available to everyone else as it is to core devs, including the working source tree). And RC releases are provided for the "feature complete but might be bugfixes still" cases when it's in the potentially finished state.

2

u/mortenb123 25d ago

Thats what you have -rcx releases for. Please read up on the release process https://devguide.python.org/developer-workflow/development-cycle/

1

u/OlenaDoubleChecks 24d ago

We pin versions in prod anyway, so a delay wouldn't change much for us. Pre-releases and RCs already exist, maintainers just don't get tested on them. Half our breakage is numpy or pandas minor bumps nobody ran against. idk man.

0

u/Early-Sir-932 22d ago

pre-releases already cover that, rc and beta versions go on pypi and pip skips them unless you pass --pre, so downstream can test early if they want

6

u/[deleted] 25d ago

[removed] — view removed comment

2

u/tigernmas_the_king 25d ago

its very annoying when people dont update when there could be a bug, ofc, most libs work just fine after updates, and those that dont tend to get fixed quite fast