ansgar grunseid

definitely looks like a bug! great find! do you have time to dig into this and open a PR to fix it?

not yet unfortunately great domain support will be added with https://github.com/gruns/furl/issues/110, which i've started but not yet completed

see https://github.com/gruns/furl/issues/110 and https://github.com/gruns/furl/issues/103 in short, furl doesn't know whether to treat `staging.s3-website.us-east-1.amazonaws.com` as a path or a domain, as it can be both. so, to be unambiguous, it treats...

Is `f[0]=1&f[1]=2&f[2]=3` a commonly used query notation to represent a dictionary of values, eg `{'f': [1, 2, 3]}`? I, personally, have never seen that URL query style used before. Do...

interesting! thank you for the link! have you seen this query pattern on other sites beyond cian.ru, too? the first result of `furl('http://example.org', args={'f': [1, 2, 3]})` that comes to...

before this is implemented and added, are there any 1) ambiguous strings that are both valid IPv6 literals and valid hostnames, or 2) surprising IPv6 literals that look confusingly like...

Absolutely! Pull requests welcome. @ThatXliner Yep; the metadata was lost in the migration to `__version__.py`

Not sure; that might do it. If ```python >>> import furl >>> furl.__version__ 2.1.0 ``` works, you did it :smiley:

Hey Uday! I can't reproduce this issue with Python v3.7 and furl v2.1.0: ```python >>> from furl import furl >>> d = dict() >>> d["start_date"] = '20200301T08:00-0000' >>> d {'start_date':...

In short, `:` can be optionally encoded in the URL Query. From RFC 3986's grammar: ``` query = *( pchar / "/" / "?" ) pchar = unreserved / pct-encoded...