[Python-Dev] [python-committers] IMPORTANT - final 3.7.0 beta cutoff!
I modified the behaviour of the socketserver module: ThreadingMixIn
now waits until all threads complete and ForkingMixIn now waits until
all child processes complete
I was supposed to do something, like add an option to at least opt-in
for the old behaviour, but I didn't have the bandwidth to work on
Python 3.7 may be shipped with the new behavior and no option to get
the old behaviour (stop immediately, don't wait for
threads/processes). Any volunteer to work on these issues?
2018-04-30 21:37 GMT+02:00 Ned Deily <nad at python.org>:
> Just a reminder that 3.7.0b4 is almost upon us. Please get your
> feature fixes, bug fixes, and documentation updates in before
> 2018-04-30 ~23:59 Anywhere on Earth (UTC-12:00). That's about 16
> hours from now.
> IMPORTANT: We are now in the final phase of 3.7.0. Tomorrow's 3.7.0b4
> is the final beta planned for 3.7.0. After tomorrow, the next planned
> release is the 3.7.0 release candidate, on 2018-05-21, for final
> testing. Our goal is to have no changes between the release candidate
> and final; after rc1, changes applied to the 3.7 branch will be
> released in 3.7.1. Between now and the rc1 cutoff, please
> double-check that there are no critical problems outstanding and that
> documentation for new features in 3.7 is complete (including NEWS and
> What's New items), and that 3.7 is getting exposure and tested with
> our various platorms and third-party distributions and applications.
> Also, during the time leading up to the release candidate, we will be
> completing the What's New in 3.7 document.
> As noted before, the ABI for 3.7.0 was frozen as of 3.7.0b3. You
> should now be treating the 3.7 branch as if it were already released
> and in maintenance mode. That means you should only push the kinds of
> changes that are appropriate for a maintenance release:
> non-ABI-changing bug and feature fixes and documentation updates. If
> you find a problem that requires an ABI-altering or other significant
> user-facing change (for example, something likely to introduce an
> incompatibility with existing users' code or require rebuilding of
> user extension modules), please make sure to set the b.p.o issue to
> "release blocker" priority and describe there why you feel the change
> is necessary. If you are reviewing PRs for 3.7 (and please do!), be
> on the lookout for and flag potential incompatibilities (we've all
> made them).
> Thanks again for all of your hard work towards making 3.7.0 yet
> another great release - coming to a website near you on 06-15!
> Ned Deily
> nad at python.org -- 
> python-committers mailing list
> python-committers at python.org
> Code of Conduct: https://www.python.org/psf/codeofconduct/