Re: [Python-Dev] Concerns about method overriding and subclassing with dataclasses

2018-01-21 Thread Eric V. Smith
On 1/7/2018 12:25 PM, Guido van Rossum wrote: On Sun, Jan 7, 2018 at 9:09 AM, Eric V. Smith > wrote: On 1/3/2018 1:17 PM, Eric V. Smith wrote: I’ll open an issue after I have time to read this thread and comment on it.

Re: [Python-Dev] PEP 567 v3

2018-01-21 Thread Koos Zevenhoven
On Thu, Jan 18, 2018 at 3:53 AM, Yury Selivanov wrote: ​[] > > Given the time frame of the Python 3.7 release schedule it was decided > to defer this proposal to Python 3.8. > ​It occurs to me that I had misread this to refer to the whole PEP. Although I thought

Re: [Python-Dev] Positional-only parameters in Python

2018-01-21 Thread Mario Corchero
Ups, indeed, totally missed it. Removed it from https://github.com/mariocj89/peps/blob/pep-pos-only/pep-.rst On 21 January 2018 at 21:44, Larry Hastings wrote: > > > On 01/21/2018 05:59 AM, Mario Corchero wrote: > > Credit for making left option groups higher precedence

Re: [Python-Dev] Positional-only parameters in Python

2018-01-21 Thread Larry Hastings
On 01/21/2018 05:59 AM, Mario Corchero wrote: Credit for making left option groups higher precedence goes to Nick Coghlan. (Conversation in person at PyCon US 2013.) Actually Argument Clinic has always given left option groups higher precedence.  This theoretically allows Argument Clinic to

Re: [Python-Dev] sys.settrace does not produce events for C functions

2018-01-21 Thread Guido van Rossum
As I posted to the issue: The reason not to pass C calls to the tracing function is that tracing exists to support pdb and other debuggers, and pdb only cares about tracing through Python code. So the docs should be updated. On Sun, Jan 21, 2018 at 11:40 AM, Pablo Galindo Salgado

[Python-Dev] sys.settrace does not produce events for C functions

2018-01-21 Thread Pablo Galindo Salgado
The docs for sys.settrace mention that: >> event is a string: 'call', 'line', 'return', 'exception', >> 'c_call', 'c_return', or 'c_exception' But in the code for ceval.c the only point where call_trace is invoked with PyTrace_C_CALL or PyTrace_C_RETURN is under the C_TRACE macro. In this macro

Re: [Python-Dev] Positional-only parameters in Python

2018-01-21 Thread Mario Corchero
Thanks, Oleg! Fixed that and a bunch more typos in the GitHub document. https://github.com/mariocj89/peps/blob/pep-pos-only/pep-.rst On 21 January 2018 at 14:16, Oleg Broytman wrote: > Hi! A few minor corrections below. > > On Sun, Jan 21, 2018 at 01:59:49PM +, Mario

Re: [Python-Dev] Positional-only parameters in Python

2018-01-21 Thread Oleg Broytman
Hi! A few minor corrections below. On Sun, Jan 21, 2018 at 01:59:49PM +, Mario Corchero wrote: > Author: Larry Hastings , Pablo Galindo > , Mario Corchero ^ Add a space or a few here - this is the way for

Re: [Python-Dev] Positional-only parameters in Python

2018-01-21 Thread Mario Corchero
Here is the proposal we have worked on (Pablo and I). I've added Larry as co-author given that a good chunk of the content and the idea comes from his PEP. Larry, if you don't want to appear as such please let us know. Thanks! Rendered content: