Python 3.8.0b1 not there yet
tl;dr - We're on it but Beta 1 is special and the buildbots need more cowbell^H^H more green.
Today Victor's been very active helping getting the stable buildbots green. Two main issues that were blocking Beta 1 were: a coredump in new functionality for subinterpreters (BPO-33608) and asyncio tests being flaky by altering the environment (BPO-37137).
The former was solved by reverting the offending change. Victor did merge a few changes to help with the latter but it's sadly still red on the stable buildbots.
While it's "just" an altered environment, I'd feel really bad about releasing the first beta with three stable buildbots in the red. Thankfully, Andrew Svetlov is looking at the problem as you're reading this.
Another thing about Beta 1 is that it's the moment where the branch is cut, which also triggers quite a few required configuration changes in CI, Github, Buildbot, Roundup, and so on. Ned has been helping me understand the full scope of this today.
**Please avoid pushing last minute changes while we are trying to get the stable buildbots all green for release. Thanks for your understanding!**
- Ł
Hi,
Does this mean that https://github.com/python/cpython/pull/6641 isn't going to get in 3.8?
Cheers, Mark.
On 03/06/2019 18:56, Łukasz Langa wrote:
tl;dr - We're on it but Beta 1 is special and the buildbots need more cowbell^H^H more green.
Today Victor's been very active helping getting the stable buildbots green. Two main issues that were blocking Beta 1 were: a coredump in new functionality for subinterpreters (BPO-33608) and asyncio tests being flaky by altering the environment (BPO-37137).
The former was solved by reverting the offending change. Victor did merge a few changes to help with the latter but it's sadly still red on the stable buildbots.
While it's "just" an altered environment, I'd feel really bad about releasing the first beta with three stable buildbots in the red. Thankfully, Andrew Svetlov is looking at the problem as you're reading this.
Another thing about Beta 1 is that it's the moment where the branch is cut, which also triggers quite a few required configuration changes in CI, Github, Buildbot, Roundup, and so on. Ned has been helping me understand the full scope of this today.
**Please avoid pushing last minute changes while we are trying to get the stable buildbots all green for release. Thanks for your understanding!**
- Ł
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Le mar. 4 juin 2019 à 16:45, Mark Shannon mark@hotpy.org a écrit :
Does this mean that https://github.com/python/cpython/pull/6641 isn't going to get in 3.8?
Maybe we can consider to put it in beta2, but please don't push any further intrusive change before beta1!
Victor
On 6/4/2019 12:12 PM, Victor Stinner wrote:
Le mar. 4 juin 2019 à 16:45, Mark Shannon mark@hotpy.org a écrit :
Does this mean that https://github.com/python/cpython/pull/6641 isn't going to get in 3.8?
Maybe we can consider to put it in beta2, but please don't push any further intrusive change before beta1!
May I merge non-intrusive changes (to IDLE)?
You can but they won't be in beta1 anymore. I am waiting for .exe files to branch 3.8 out. Sources and Mac binaries for beta 1 are already built.
- Ł
On 4 Jun 2019, at 21:43, Terry Reedy tjreedy@udel.edu wrote:
On 6/4/2019 12:12 PM, Victor Stinner wrote:
Le mar. 4 juin 2019 à 16:45, Mark Shannon mark@hotpy.org a écrit :
Does this mean that https://github.com/python/cpython/pull/6641 isn't going to get in 3.8?
Maybe we can consider to put it in beta2, but please don't push any further intrusive change before beta1!
May I merge non-intrusive changes (to IDLE)?
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On 4 Jun 2019, at 21:43, Terry Reedy tjreedy@udel.edu wrote:
May I merge non-intrusive changes (to IDLE)?On 6/4/2019 3:46 PM,
Łukasz Langa wrote:
You can but they won't be in beta1 anymore. I am waiting for .exe files to branch 3.8 out. Sources and Mac binaries for beta 1 are already built.
Sounds like it would be better to wait until there is a 3.8 branch and a working Backport 3.8 label.
On 4 Jun 2019, at 22:05, Terry Reedy tjreedy@udel.edu wrote:
On 4 Jun 2019, at 21:43, Terry Reedy tjreedy@udel.edu wrote:
May I merge non-intrusive changes (to IDLE)?On 6/4/2019 3:46 PM,
Łukasz Langa wrote:
You can but they won't be in beta1 anymore. I am waiting for .exe files to branch 3.8 out. Sources and Mac binaries for beta 1 are already built.
Sounds like it would be better to wait until there is a 3.8 branch and a working Backport 3.8 label.
The branch is already there, we'll see how much fiddling is getting the backport label to work.
- Ł
On Jun 4, 2019, at 7:44 AM, Mark Shannon mark@hotpy.org wrote:
Does this mean that https://github.com/python/cpython/pull/6641 isn't going to get in 3.8?
I've been hoping for this PR to land for a good while. If it doesn't go in today, we should definitely try to get it in the next beta release.
Raymond
participants (5)
-
Mark Shannon -
Raymond Hettinger -
Terry Reedy -
Victor Stinner -
Łukasz Langa