May 10, 2016
6:29 a.m.
On 10 May 2016 at 07:57, M.-A. Lemburg <mal@egenix.com> wrote:
This looks more like an API design question than a coding style one.
This is actually a good point - at the moment, PEP 8 is a mix of coding style guidelines (i.e. how we use existing APIs) and API design guidelines (especially the parts on naming conventions and defining what is and isn't a public API). For code reviews, we want the former, but for PEP discussions we want the latter. Perhaps it would make sense to give API design guidelines a dedicated home in the developer guide, rather than overloading PEP 8 with them? Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia