Fragment handling for unknown schemes

[gazpachoking]

We use urldefrag and urlparse to deal with splitting fragments, and on python < 3.3 this doesn't work for URIs with unknown schemes, e.g. foo://bar#something

[gazpachoking]

We could provide our own versions of urlparse and urldefrag, which, on python < 3.3 appended any unknown schemes to urlparse.uses_fragment beforehand.

[gazpachoking]

Possibly also do this for urljoin and add the scheme to urlparse.uses_relative and urlparse.uses_netloc too. This would apply to python 3.3 as well.

[Julian]

Seems like the patch from http://bugs.python.org/issue9374 is probably what we want? Looks like it was backed out from being back ported to 2.7.

No?

[gazpachoking]

Yeah, that patch would fix our issue. What are you thinking, monkeypatch urlparse?

[gazpachoking]

(Well it would fix fragment issue. Combining relative uris with the base uri also works differently with unknown schemes, but I'm thinking maybe user is responsible for adding their scheme to uses_relative and uses_netloc if they need it to work like that.)

[Julian]

No need to monkey patch, just copy and paste to include it would work along with using the one we include rather than urlparse.

[gazpachoking]

Oh hmm, why was I being silly? Yes, this makes sense.