Senthil Kumaran orsenthil at gmail.com
Wed Mar 16 00:14:29 CET 2011

• Previous message: [Python-Dev] Finally switch urllib.parse to RFC3986 semantics?
• Next message: [Python-Dev] Finally switch urllib.parse to RFC3986 semantics?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Wed, Mar 16, 2011 at 7:01 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> With RFC 3986 passing its 6th birthday, and with it being well past
> its 7th by the time 3.3 comes out, can we finally switch to supporting
> the current semantics rather than the obsolete behaviour?

We do infact, support RFC 3986, expect for the cases where those
conflict with the previous RFCs. (IOW, backwards compatible).
The tests can give you a good picture here. Do you mean, we should
just do away with backwards  compatibility? Or you had anything else
specifically in mind?

-- 
Senthil

---

• Previous message: [Python-Dev] Finally switch urllib.parse to RFC3986 semantics?
• Next message: [Python-Dev] Finally switch urllib.parse to RFC3986 semantics?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list