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
> 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
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
> 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
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
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
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
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 bugs, some functions like
os.waitpid() on
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),
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).
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
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
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
On 5/18/18 9:20 AM, Ivan Pozdeev via Python-Dev wrote:
> Since Python uses semantic versioning (https://semver.org), the
> criterion for "what's new-worthy" changes is simple: they are _public
> interface changes_ (which include visible changes to documented behavior).
> (I maintain that changes
On 18.05.2018 10:55, Serhiy Storchaka wrote:
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
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
17.05.18 21:43, Elvis Pranskevichus пише:
I'm working on the What's New document. Will start putting PRs in the
next few days.
Great!
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
On Thursday, May 17, 2018 2:31:37 PM EDT 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
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
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
21 matches
Mail list logo