A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133733.html below:

[Python-Dev] Treating tokenize.Untokenizer as private

[Python-Dev] Treating tokenize.Untokenizer as private [Python-Dev] Treating tokenize.Untokenizer as privateRaymond Hettinger raymond.hettinger at gmail.com
Mon Mar 31 21:51:39 CEST 2014
On Feb 18, 2014, at 1:09 PM, Terry Reedy <tjreedy at udel.edu> wrote:

> While the function could be implemented as one 70-line function, it happens to be implemented as a 4-line wrapper for a completely undocumented (Untokenizer class with 4 methods. (It is unmentioned in the doc and there are currently no docstrings.)
> 
> I view the class as a private implementation detail and would like to treat it as such, and perhaps even rename it _Untokenizer to make that clear.

Yes, that would be reasonable.


Raymond
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140331/ebe73de9/attachment.html>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4