[Python-Dev] Policy on refactoring/clean up (original) (raw)
INADA Naoki songofacandy at gmail.com
Wed Jun 27 01:40:31 EDT 2018
- Previous message (by thread): [Python-Dev] Policy on refactoring/clean up
- Next message (by thread): [Python-Dev] Policy on refactoring/clean up
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Jun 27, 2018 at 2:27 PM Jeroen Demeyer <J.Demeyer at ugent.be> wrote:
On 2018-06-27 00:02, Guido van Rossum wrote: > And TBH a desire to refactor a lot of code is often a sign of a > relatively new contributor who hasn't learned their way around the code > yet, so they tend to want to make the code follow their understanding > rather than letting their understanding follow the code.
...or it could be that the code is written the way it is only for historical reasons, instead of bei ng purposely written that way.
In this time, I suppose you thought .c <=> .h filename should be matched. And we don't think so.
Header files are organized for exposing APIs, and source files are organized for implementing the APIs. Since goal is different, they aren't match ed always.
Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180627/7c23ff1f/attachment-0001.html>
- Previous message (by thread): [Python-Dev] Policy on refactoring/clean up
- Next message (by thread): [Python-Dev] Policy on refactoring/clean up
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]