Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Mark Shannon 

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
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Victor Stinner 
Le mar. 4 juin 2019 à 16:45, Mark Shannon  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
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Raymond Hettinger 



> On Jun 4, 2019, at 7:44 AM, Mark Shannon  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
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Terry Reedy 

On 6/4/2019 12:12 PM, Victor Stinner wrote:

Le mar. 4 juin 2019 à 16:45, Mark Shannon  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
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Łukasz Langa 
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  wrote:
> 
> On 6/4/2019 12:12 PM, Victor Stinner wrote:
>> Le mar. 4 juin 2019 à 16:45, Mark Shannon  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
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Terry Reedy 

> On 4 Jun 2019, at 21:43, Terry Reedy  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.



___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Łukasz Langa 

> On 4 Jun 2019, at 22:05, Terry Reedy  wrote:
> 
> > On 4 Jun 2019, at 21:43, Terry Reedy  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.

- Ł



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.0b1 is now available for testing

2019-06-04 Thread Łukasz Langa 
The time has come for Python 3.8.0b1:
https://www.python.org/downloads/release/python-380b1/ 

This release is the first of four planned beta release previews. Beta release 
previews are intended to give the wider community the opportunity to test new 
features and bug fixes and to prepare their projects to support the new feature 
release. The next pre-release of Python 3.8 will be 3.8.0b2, currently 
scheduled for 2019-07-01.


Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.8 during the beta phase and report issues found to the Python bug tracker 
 as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and 
no code changes after 3.8.0rc1, the release candidate. To achieve that, it will 
be extremely important to get as much exposure for 3.8 as possible during the 
beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.


A new challenger has appeared!

With the release of Python 3.8.0b1, development started on Python 3.9. The 
“master” branch in the cpython repository now tracks development of 3.9 while 
Python 3.8 received its own branch, called simply “3.8”.


Acknowledgments

As you might expect, creating new branches triggers a lot of changes in 
configuration for all sorts of tooling that we’re using. Additionally, the 
inevitable deadline for new features caused a flurry of activity that tested 
the buildbots to the max. The revert hammer got  used more than once.

I would not be able to make this release available alone. Many thanks to the 
fearless duo of Pablo Galindo Salgado and Victor Stinner for spending tens of 
hours during the past week working on getting the buildbots green for release. 
Seriously, that took a lot of effort. We are all so lucky to have you both.

Thanks to Andrew Svetlov for his swift fixes to asyncio and to Yury Selivanov 
for code reviews, even when jetlagged. Thanks to Julien Palard for untangling 
the documentation configs. Thank you to Zachary Ware for help with buildbot and 
CI configuration. Thanks to Mariatta for helping with the bots. Thank you to 
Steve Dower for delivering the Windows installers.

Most importantly though, huge thanks to Ned Deily who not only helped me 
understand the scope of this special release but also did some of the grunt 
work involved.

Last but not least, thanks to you for making this release more meaty than I 
expected. There’s plenty of super exciting changes in there. Just take a look 
at “What’s New ”!


One more thing

Hey, fellow Core Developer, Beta 2 is in four weeks. If your important new 
feature got reverted last minute, or you decided not to merge due to inadequate 
time, I have a one time offer for you (restrictions apply). If you:

find a second core developer champion for your change; and
in tandem you finish your change complete with tests and documentation before 
Beta 2
then I will let it in. I’m asking for a champion because it’s too late now for 
changes with hasty design or code review. And as I said, restrictions apply. 
For instance, at this point changes to existing APIs are unlikely to be 
accepted. Don’t start new work with 3.8 in mind. 3.9 is going to come sooner 
than you think!



- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/