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
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 Windows (if I rec
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
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 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"?
> 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
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
> 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
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.
>> [...]
>>
>>
Hi,
While PEP 574 (pickle protocol 5 with out-of-band data) is still in
draft status, I've made available an implementation in branch "pickle5"
in my GitHub fork of CPython:
https://github.com/pitrou/cpython/tree/pickle5
Also I've published an experimental backport on PyPI, for Python 3.6
and 3.
Link to the PEP:
"PEP 574 -- Pickle protocol 5 with out-of-band data"
https://www.python.org/dev/peps/pep-0574/
Victor
2018-05-24 19:57 GMT+02:00 Antoine Pitrou :
>
> Hi,
>
> While PEP 574 (pickle protocol 5 with out-of-band data) is still in
> draft status, I've made available an implementation
On Thu, 2018-05-17 at 15:18 +0300, Serhiy Storchaka wrote:
> Does anyone has the full copy of the PyXML repository, with the
> complete history?
>
> This library was included in Python 2.1 as the xml package and is
> not maintained as a separate project since 2004. It's home on
> SourceForge was r
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
13 matches
Mail list logo
