Ansgar Grunseid

thank you for opening this issue! great catch, and thank you for providing the super helpful links for context let's fix this; consistency is key. do you have time to...

do you have the time and bandwidth to add types to icecream? 🙂

@palfrey thank you for your efforts here! 🙌

great find! this appears to be two issues. issue #1: '127.0.0.1:8080/a/b'` is actually ambiguous: it could be parsed as * host `127.0.0.1`, port `8080`, and path `/a/b` or as *...

this would be handy indeed. all for this improvement digging in, what other side effects might subclassing `Text` have?

> For one, 'asdf'.join and furl('asdf').join are completely different things. exactly as i was curious about 🙂 > I've since taken out my "workaround" above and posited changes from the...

Absolutely not by design. Wonderful catch. I'll rectify this shortly.

I, too, got confused. This is intentional behavior. Albeit a bit of an initial head scratcher. See https://github.com/gruns/furl/issues/85 and my detailed answer here https://github.com/gruns/furl/issues/85#issuecomment-293483792. Long story short: `www.example.com` looks like...

Resolution of this Issue tied with the resolution of #110.

this isn't an outright bug, as `'https://www.baidu.com/aaa//bbbb/ccc'`, with back to back `//`, is a perfectly valid url. furl doesn't prevent you from creating such urls. you can always do ```py...