report at bugs
May 9, 2012, 4:44 AM
Post #6 of 15
Lars Gustäbel <lars [at] gustaebel> added the comment:
[issue13815] tarfile.ExFileObject can't be wrapped using io.TextIOWrapper
[In reply to]
In an earlier draft of my patch, I had kept ExFileObject as a subclass of BufferedReader, but I later decided against it. To use BufferedReader directly is in my opinion the cleaner solution.
I admit that the change is not fully backward compatible. But a user can still write code that works for both 3.3 and the versions before. If he didn't subclass ExFileObject his code doesn't even need a change. If he subclassed ExFileObject, he might have a problem in either case: either the ExFileObject class is missing, or he may be unable to use it the way he did before, because all that's left of it is a stub subclass of BufferedReader.
I am well aware that backward compatibility is most important, but I think it must still be allowed to change internal (and undocumented) APIs every now and then to clean things up a little.
And of course, I did a code search before too, and found no code using ExFileObject. This actually doesn't surprise me, as there is really not much you can do with it.
Python tracker <report [at] bugs>
Python-bugs-list mailing list