Re: [Python-Dev] PEP 7 and braces { .... } on if

2017-06-06 Thread Ethan Furman
On 06/06/2017 05:30 PM, Barry Warsaw wrote: On Jun 05, 2017, at 08:19 AM, Ethan Furman wrote: I would format that as: if (PyErr_WarnFormat( PyExc_DeprecationWarning, 1, "invalid escape sequence '\\%c'", *first_i

Re: [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7

2017-06-06 Thread Nick Coghlan
On 6 June 2017 at 20:08, Nathaniel Smith wrote: > On Mon, Jun 5, 2017 at 8:49 PM, Nick Coghlan wrote: >> The reason this kind of approach is really attractive to >> redistributors from a customer risk management perspective is that >> like gevent's monkeypatching of synchronous networking APIs, i

Re: [Python-Dev] PEP 7 and braces { .... } on if

2017-06-06 Thread Rob Cliffe
On 07/06/2017 01:30, Barry Warsaw wrote: On Jun 05, 2017, at 08:41 AM, Serhiy Storchaka wrote: the example above), and the following code is enough readable: if (PyErr_WarnFormat(PyExc_DeprecationWarning, 1, "invalid escape sequence '\\%c'",

Re: [Python-Dev] PEP 7 and braces { .... } on if

2017-06-06 Thread Barry Warsaw
On Jun 05, 2017, at 07:00 AM, Skip Montanaro wrote: >Wow, this discussion takes me back. Glad I don't have to check out >comp.lang.c to get my brace placement fix. Life is better without braces! -Barry ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] PEP 7 and braces { .... } on if

2017-06-06 Thread Barry Warsaw
On Jun 05, 2017, at 08:41 AM, Serhiy Storchaka wrote: >the example above), and the following code is enough readable: > > if (PyErr_WarnFormat(PyExc_DeprecationWarning, 1, > "invalid escape sequence '\\%c'", > *first_invalid_escape)

Re: [Python-Dev] The untuned tunable parameter ARENA_SIZE

2017-06-06 Thread Chris Barker
On Mon, Jun 5, 2017 at 8:10 PM, Tim Peters wrote: > [Tim] > >> So at most 9 arenas ("highwater mark") were ever simultaneously > allocated [by the > >> time the REPL prompt appeared in a 64-bit 3.6.1].. > > > ... though not completely off-base. > > Yes, 9 is in the ballpark of 16. > > > I think

Re: [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7

2017-06-06 Thread Jim Baker
With Nick's suggestion of _tls_bootstrap, this has certainly become more complicated. I'm still thinking of the ramifications for future Jython 2.7 support, if Python dev goes down this path. It still seems easier to me to avoid exposing the SSLObject/MemoryBIO model to 2.7 and instead concentrate

Re: [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7

2017-06-06 Thread Nathaniel Smith
On Mon, Jun 5, 2017 at 8:49 PM, Nick Coghlan wrote: > The reason this kind of approach is really attractive to > redistributors from a customer risk management perspective is that > like gevent's monkeypatching of synchronous networking APIs, it's > *opt-in at runtime*, so the risk of our accident