On Mon, Aug 26, 2013 at 9:21 AM, Antoine Pitrou <solip...@pitrou.net> wrote:
> Le Mon, 26 Aug 2013 09:14:38 -0700, > Eli Bendersky <eli...@gmail.com> a écrit : > > > > Antoine, you opted out of the tracker issue but I feel it's fair to > > let you know that after a lot of discussion with Nick and Stefan (*), > > we've settled on renaming the input methods to feed & close, and the > > output method to read_events. We are also considering a different > > name for the class. > > Fair enough. > > > As for the class name, IncrementalParser is ambiguous because it's not > > immediately clear which side is incremental. Input or output? > > Both are :-) > > Yes, exactly :-) "Incremental", though, seems to support the conjecture that it's the input. Which is true, but, since XMLParser is also "incremental" in this sense, slightly confusing. As a more anecdotal piece of evidence: when the issue was reopened, I myself at first got confused by exactly this point because I forgot all about this in the months that passed since the commit. And I recalled that when I initially reviewed your patch, I got confused too :-) That would suggest one of two things: (1) The name is indeed confusing or (2) I'm stupid. The fact that Nick also got confused when trying a cursory understanding of the documentation cams me down w.r.t. (2). Back to the discussion, my new favorite is NonblockingParser. Because its input side is exactly similar to XMLParser, the "Nonblocking" in the name points to the difference in output, which is correct. As the popular quote says, "There are only two hard problems in Computer Science: cache invalidation and naming things." Eli
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
