[Python-Dev] building extensions as builtins is broken in 3.7

Hi, I am working on the release blocker https://bugs.python.org/issue32232. I tried to apply the patch proposed by Matthias Klose and I found that it works on Unix but it fails to build on Windows (probably because circular imports). I tried to add some tests but after some work on the problem

Re: [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

On Mon, Apr 2, 2018 at 3:57 PM Lukasz Langa wrote: > > > On Apr 2, 2018, at 2:13 PM, Antoine Pitrou wrote: > > > > On Mon, 2 Apr 2018 13:48:46 -0700 > > Lukasz Langa wrote: > >> Pickle protocol version 4.0 was originally defined back in

Re: [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

> On Apr 2, 2018, at 2:13 PM, Antoine Pitrou wrote: > > On Mon, 2 Apr 2018 13:48:46 -0700 > Lukasz Langa wrote: >> Pickle protocol version 4.0 was originally defined back in PEP 3154 and >> shipped as part of Python 3.4 back in 2011. Yet it's still not

Re: [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

Given that, go ahead and change in master (3.8). On Mon, Apr 2, 2018 at 3:13 PM Christian Heimes wrote: > On 2018-04-02 22:48, Lukasz Langa wrote: > > Pickle protocol version 4.0 was originally defined back in PEP 3154 and > shipped as part of Python 3.4 back in 2011. Yet

Re: [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

On 2018-04-02 22:48, Lukasz Langa wrote: > Pickle protocol version 4.0 was originally defined back in PEP 3154 and > shipped as part of Python 3.4 back in 2011. Yet it's still not the default. > There's a number of things that would run faster with it like multiprocessing. > > This is too late

Re: [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

On Mon, 2 Apr 2018 13:48:46 -0700 Lukasz Langa wrote: > Pickle protocol version 4.0 was originally defined back in PEP 3154 and > shipped as part of Python 3.4 back in 2011. Yet it's still not the default. Because we want pickles produced with the default to be readable by

[Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?

Pickle protocol version 4.0 was originally defined back in PEP 3154 and shipped as part of Python 3.4 back in 2011. Yet it's still not the default. There's a number of things that would run faster with it like multiprocessing. This is too late for 3.7 which is a shame but can we at least bump

Re: [Python-Dev] IDLE colorizer

Heh. The good old manual approach. :-) How bad indeed? >>> from idlelib import colorizer; colorizer.make_pat() from idlelib import colorizer; colorizer.make_pat()

Re: [Python-Dev] IDLE colorizer

On 2018-04-02 05:43, Guido van Rossum wrote: My question for you: how on earth did you find this?! Speaking of a needle in a haystack. Did you run some kind of analysis program that looks for regexprs? (We've received some good reports from someone who did that looking for possible DoS

[Python-Dev] [Crosspost from python-committers] Announcing: signups are open for the 2018 Python Language Summit

It’s that time again: time to start thinking about the Python Language Summit!  The 2018 summit will be held on Wednesday, May 9, from 10am to 4pm, at the Huntington Convention Center in Cleveland, Ohio, USA.  Your befezzled and befuddled hosts Barry and Larry will once more be behind the

Re: [Python-Dev] Nuking wstr [Re: How can we use 48bit pointer safely?]

> > Of course, the question is whether all this matters. Is it important > to save 8 bytes on each unicode object? Only testing would tell. > Last year, I tried to profile memory usage of web application in my company.

Re: [Python-Dev] Nuking wstr [Re: How can we use 48bit pointer safely?]

Some of APIs are stated as "Deprecated since version 3.3, will be removed in version 4.0:". e.g. https://docs.python.org/3/c-api/unicode.html#c.PyUnicode_AS_UNICODE So we will remove them (and wstr) at Python 4.0. ___ Python-Dev mailing list