[python-committers] 3.7.0rc1 Delayed [was] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ned Deily
On May 24, 2018, at 03:23, Ned Deily wrote: > On May 23, 2018, at 09:13, Ned Deily wrote: >> On May 23, 2018, at 07:45, Serhiy Storchaka wrote: >>> Is it possible to add yet one beta instead? >>> CI was broken for few latest days, tests are not passed on my computer >>> still (and fail on some

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

2018-05-24 Thread Matthias Klose
On 24.05.2018 20:09, Ned Deily wrote: > On May 24, 2018, at 13:46, Larry Hastings wrote: >> On 05/24/2018 10:08 AM, Ned Deily wrote: >>> If you (or anyone else) feels strongly enough about it, you should re-open >>> the issue now and make it as a "release blocker" and we should discuss the >>> i

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

2018-05-24 Thread Ned Deily
On May 24, 2018, at 13:46, Larry Hastings wrote: > On 05/24/2018 10:08 AM, Ned Deily wrote: >> If you (or anyone else) feels strongly enough about it, you should re-open >> the issue now and make it as a "release blocker" and we should discuss the >> implications and possible plans of action in

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Donald Stufft
> On May 24, 2018, at 2:05 PM, Antoine Pitrou wrote: > > > Le 24/05/2018 à 20:02, Brett Cannon a écrit : >>> Just trying to >>> understand how Discourse would be different enough to solve the issue >>> you're having. >> >>Which issue exactly? Zulip is decent as a chat system. It wouldn'

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Antoine Pitrou
Le 24/05/2018 à 20:02, Brett Cannon a écrit : > > Just trying to > > understand how Discourse would be different enough to solve the issue > > you're having. > > Which issue exactly?  Zulip is decent as a chat system.  It wouldn't > really work for PEP discussions, IMO.  That'

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Brett Cannon
On Thu, 24 May 2018 at 10:45 Antoine Pitrou wrote: > > Le 24/05/2018 à 18:54, Brett Cannon a écrit : > > > > I don't think Zulip works for structured discussion. I also find it > > slightly less usable than I expected. > > > > Why specifically? Do you still find IRC more usable? > > Um,

[python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

2018-05-24 Thread Larry Hastings
On 05/24/2018 10:08 AM, Ned Deily wrote: If you (or anyone else) feels strongly enough about it, you should re-open the issue now and make it as a "release blocker" and we should discuss the implications and possible plans of action in the issue. About that.  According to the Python Dev Gui

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Antoine Pitrou
Le 24/05/2018 à 18:54, Brett Cannon a écrit : > > I don't think Zulip works for structured discussion.  I also find it > slightly less usable than I expected. > > Why specifically? Do you still find IRC more usable? Um, no. But I find Zulip's way of grouping discussions by day *then* b

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Brett Cannon
On Tue, 22 May 2018 at 13:52 Barry Warsaw wrote: > On May 22, 2018, at 12:44, Guido van Rossum wrote: > > > > Hm, what's the cost of those extra repos? As long as they have > consistent names (e.g. pep-1234) they're easy to ignore right? Or does > GitHub have a quota of repos per org? > > I thin

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ned Deily
On May 24, 2018, at 12:26, Serhiy Storchaka wrote: > 24.05.18 19:02, Ned Deily пише: >> On May 24, 2018, at 11:35, Serhiy Storchaka wrote: >>> I have doubts about two issues. I feel the responsibility for them because >>> I had the opportunity to solve them before, but I lost it. >> [...] >> >>

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Brett Cannon
On Tue, 22 May 2018 at 18:07 Steven D'Aprano wrote: > On Tue, May 22, 2018 at 05:58:39PM -0400, Donald Stufft wrote: > > > > > On May 22, 2018, at 5:50 PM, Victor Stinner > wrote: > > > > > > IMHO the discussions on the PEP 572 became a mess because nobody > > > wanted to moderate the discussion

Re: [python-committers] A different way to focus discussions

2018-05-24 Thread Brett Cannon
On Tue, 22 May 2018 at 13:10 Antoine Pitrou wrote: > > Le 22/05/2018 à 22:06, Brett Cannon a écrit : > > > > > > On Tue, 22 May 2018 at 12:07 Antoine Pitrou > > wrote: > > > > > > Le 22/05/2018 à 20:58, Barry Warsaw a écrit : > > > > > >> Thoughts? (We can

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ivan Levkivskyi
> But cases not supported before 3.7 (like List[int]) now produce fragile pickles. List[int] pickled in 3.7 can't be un-pickled in 3.6, but I wouldn't worry too much about this because it never worked in 3.6. I remember you proposed using __getitem__ in __reduce__, but I am not sure it is a better

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Serhiy Storchaka
24.05.18 19:02, Ned Deily пише: On May 24, 2018, at 11:35, Serhiy Storchaka wrote: I have doubts about two issues. I feel the responsibility for them because I had the opportunity to solve them before, but I lost it. [...] Serhiy, what are the bugs.python.org issue numbers for these? Are th

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ivan Levkivskyi
> 2. Pickle support in typing is not perfect. I was going to fix it (I had almost ready code), but lost a chance of doing this before. It can be changed in 3.7.1, but this means that pickles of some derived typing types created in 3.7.0 will be not compatible with future versions (may be 3.7.1 will

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ned Deily
On May 24, 2018, at 11:35, Serhiy Storchaka wrote: > I have doubts about two issues. I feel the responsibility for them because I > had the opportunity to solve them before, but I lost it. [...] Serhiy, what are the bugs.python.org issue numbers for these? Are they marked as "release blocker"?

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Serhiy Storchaka
24.05.18 10:23, Ned Deily пише: So this *is* really your last chance: if you know of any true releasing blocking issues for 3.7.0, you have about 12 more hours to log it in the bug tracker as a "release blocker". I'll send out an email once we start the release manufacturing. Any merges to the 3.

Re: [python-committers] [Python-Dev] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ned Deily
On May 24, 2018, at 07:26, Victor Stinner wrote: > 2018-05-24 9:23 GMT+02:00 Ned Deily : >> Any merges to the 3.7 branch after >> that will be released in 3.7.1 which we tentatively are planning to >> ship sometime before the end of July (< 2018-07-31). > I recall that Python 3.6.0 was full of bug

Re: [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 Thread Ned Deily
On May 23, 2018, at 09:13, Ned Deily wrote: > On May 23, 2018, at 07:45, Serhiy Storchaka wrote: >> Is it possible to add yet one beta instead? >> CI was broken for few latest days, tests are not passed on my computer still >> (and fail on some buildbots), updating What's New exposed new feature