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.
>> [...]
>>
>>
> 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
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
> 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
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"?
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.
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
On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
> 15.05.18 14:51, Ned Deily пише:
>> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
>> feature fixes, bug fixes, and documentation updates in before
>> 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days
>> f
Ah, Python doesn't compile on Windows anymore :-)
https://bugs.python.org/issue33614
Victor
2018-05-23 14:16 GMT+02:00 Victor Stinner :
> 2018-05-23 13:45 GMT+02:00 Serhiy Storchaka :
>> CI was broken for few latest days, tests are not passed on my computer still
>> (and fail on some buildbots),
2018-05-23 13:45 GMT+02:00 Serhiy Storchaka :
> CI was broken for few latest days, tests are not passed on my computer still
> (and fail on some buildbots), (...)
I looked at buildbots and I confirm that many of the 3.x buildbots are red:
AMD64 FreeBSD 10.x Shared 3.x
AMD64 Windows8.1 Non-Debug 3
2018-05-23 13:47 GMT+02:00 Antoine Pitrou :
> Also there's https://bugs.python.org/issue33612 which appears quite
> critical.
Can someone please have a look at my socketserver change?
https://github.com/python/cpython/pull/6911
bpo-31151 changed ForkingMixIn and bpo-31233 changed ThreadingMixIn t
Also there's https://bugs.python.org/issue33612 which appears quite
critical.
Regards
Antoine.
Le 23/05/2018 à 13:45, Serhiy Storchaka a écrit :
> 15.05.18 14:51, Ned Deily пише:
>> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
>> feature fixes, bug fixes, and documentat
15.05.18 14:51, Ned Deily пише:
This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
feature fixes, bug fixes, and documentation updates in before
2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days
from now. We will then tag and produce the 3.7.0 release candidat
17.05.18 21:39, Brett Cannon пише:
Maybe we should start thinking about flagging PRs or issues as needing
a What's New entry to help track when they need one, or always expect
it in a PR and ignore that requirement when a 'skip whats new' label
is applied. That would at least make it easier to
On Thu, 17 May 2018 at 14:31 Serhiy Storchaka wrote:
> 15.05.18 14:51, Ned Deily пише:
> > This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
> > feature fixes, bug fixes, and documentation updates in before
> > 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 day
Elvis has been working on the What’s New doc at the sprints this week. He
should be checking in his edits soon. Stay tuned!
--
Ned Deily
n...@python.org -- []
> On May 17, 2018, at 14:31, Serhiy Storchaka wrote:
>
> 15.05.18 14:51, Ned Deily пише:
>> This is it! We are down to THE
15.05.18 14:51, Ned Deily пише:
This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
feature fixes, bug fixes, and documentation updates in before
2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days
from now. We will then tag and produce the 3.7.0 release candidat
This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
feature fixes, bug fixes, and documentation updates in before
2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days
from now. We will then tag and produce the 3.7.0 release candidate.
Our goal continues been to be t
18 matches
Mail list logo
