Re: [Python-Dev] Treating tokenize.Untokenizer as private

2014-03-31 Thread Eric Snow
On Mon, Mar 31, 2014 at 1:45 PM, Terry Reedy wrote: > On 3/31/2014 2:30 PM, Eric Snow wrote: >> Is this still an open question, Terry? > > > It is not currently for #9974 because after consideration of two proposed > patches (one part of another issue), I decided that the conditions being > guarde

Re: [Python-Dev] Treating tokenize.Untokenizer as private

2014-03-31 Thread Raymond Hettinger
On Feb 18, 2014, at 1:09 PM, Terry Reedy 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 d

Re: [Python-Dev] Treating tokenize.Untokenizer as private

2014-03-31 Thread Terry Reedy
On 3/31/2014 2:30 PM, Eric Snow wrote: On Tue, Feb 18, 2014 at 2:09 PM, Terry Reedy wrote: I am working through the multiple bugs afflicting tokenize.untokenize, which is described in the tokenize doc and has an even longer docstring. While the function could be implemented as one 70-line funct

Re: [Python-Dev] Treating tokenize.Untokenizer as private

2014-03-31 Thread Eric Snow
On Tue, Feb 18, 2014 at 2:09 PM, Terry Reedy wrote: > I am working through the multiple bugs afflicting tokenize.untokenize, which > is described in the tokenize doc and has an even longer docstring. While the > function could be implemented as one 70-line function, it happens to be > implemented