[Python-Dev] Re: Exposing Tools/parser/unparse.py in the stdlib?

2019-11-20 Thread Brett Cannon
Victor Stinner wrote: > Le mar. 19 nov. 2019 à 22:12, Pablo Galindo Salgado > pablog...@gmail.com a écrit : > > Float infinity > > is replaced with 1e309. Again, maybe someone wants > > to render this differently? It sounds like an arbitrary choice (which > > "works" as expected). > > That is not t

[Python-Dev] Re: [RELEASE] Python 3.9.0a1 available for testing

2019-11-20 Thread Steve Dower
On 19Nov2019 1708, Łukasz Langa wrote: Go get it here: https://www.python.org/downloads/release/python-390a1/ Is it intentional that this link does not appear on https://www.python.org/download/pre-releases/ ? Cheers, Steve __

[Python-Dev] Re: Exposing Tools/parser/unparse.py in the stdlib?

2019-11-20 Thread Nick Coghlan
On Thu., 21 Nov. 2019, 3:30 am Brett Cannon, wrote: > Victor Stinner wrote: > > > It's mostly to minimize the number of imports on "import ast". unparse > > requires extra imports like tokenize which has also tons of > > dependencies. > > Why are you specifically worried about that? If you're doi

[Python-Dev] Re: [RELEASE] Python 3.9.0a1 available for testing

2019-11-20 Thread Łukasz Langa
Good catch, I didn't update that. -- Best regards, Łukasz Langa > On 20 Nov 2019, at 18:59, Steve Dower wrote: > > On 19Nov2019 1708, Łukasz Langa wrote: >> Go get it here: https://www.python.org/downloads/release/python-390a1/ >> > >

[Python-Dev] Re: Exposing Tools/parser/unparse.py in the stdlib?

2019-11-20 Thread Pablo Galindo Salgado
Opened https://bugs.python.org/issue38870 to track this. On Tue, 19 Nov 2019 at 00:40, Pablo Galindo Salgado wrote: > Hi, > > What do people feel about exposing Tools/parser/unparse.py in the standard > library? Here is my initial rationale: > > * The tool already needs to be maintained and upda

[Python-Dev] Re: Dangerous default value for reuse_address in asyncio loop.create_datagram_endpoint()

2019-11-20 Thread Giampaolo Rodola'
SO_REUSEADDR was controversial also for socket.create_server(). In the end I concluded the best solution was to not expose a reuse_address parameter. See: https://github.com/python/cpython/blob/94e165096fd65e8237e60de570fb609604ab94c9/Lib/socket.py#L891-L899 It must be noted that right now also as

[Python-Dev] Re: Hold multiple tracebacks per-object in tracemalloc

2019-11-20 Thread Sümer Cip
Thanks Victor, I have a better understanding of tracemalloc internals. On Tue, Nov 19, 2019 at 10:07 PM Victor Stinner wrote: > Hi, > > Le mar. 19 nov. 2019 à 18:33, Sümer Cip a écrit : > > First of all, I would like to thank for such a useful tool for debugging > memory issues. I am pretty pro