[issue13460] urllib methods should demand unicode, instead demand str

R. David Murray added the comment: Well, most of the point of Python3 is that the string type *is* unicode, which is what I meant by saying that you probably wanted Python3 in order to solve your concern :) There are still a few bugs to work out in the wire-protocol/unicode interface in Pyth

[issue13460] urllib methods should demand unicode, instead demand str

Tyler Starke added the comment: Nevermind. I had to download the source to see that it encodes to 'utf-8', or a passed encoding method, in the methods that are causing problems in 2.6.5. -- ___ Python tracker ___

[issue13460] urllib methods should demand unicode, instead demand str

Tyler Starke added the comment: well that was closed fast. I noticed in the docs that Python 3 demands a str type also. -- ___ Python tracker ___ __

[issue13460] urllib methods should demand unicode, instead demand str

R. David Murray added the comment: I suspect you want to be using Python3, then. Although it is nowhere near as simple as that...even with Python3 you still sometimes have to deal with the fact that the wire protocol is bytes. -- nosy: +r.david.murray resolution: -> out of date stat

[issue13460] urllib methods should demand unicode, instead demand str

New submission from Tyler Starke : It seems bad practice for urllib methods to demand a str instance and they should demand a unicode instance. By demanding a str instance the default behavior is too demanding, for the web space it is being used, for the English language. We would want Python