Ansgar Grunseid
Ansgar Grunseid
ex: ```python >>> f = furl('https://www.google.com/hello') >>> f.copy().set(scheme=None, netloc=None).url '//:443/hello/' ``` vs ```python >>> f = furl('https://www.google.com/hello') >>> f.copy().set(scheme=None).set(netloc=None).url '/hello' ``` and oddity with `.set(scheme=None)` ``` >>> f = furl('https://www.google.com:999/hello')...
Before v2.0.0: ```python >>> import furl >>> print(furl.__version__) '2.0.0' ``` With v2.1.0: ```python >>> import furl >>> print(furl.__version__) Traceback (most recent call last): File "", line 1, in AttributeError: module...
Once added, intelligently guess whether `furl` constructor strings are paths or domains. E.g. ```python >>> furl('www.example.com') ``` is a domain while ```python >>> furl('wwwexamplecom') ``` and ```python >>> furl('wwwexample.unknown') ```...
instead of always wrapping at `IceCreamDebugger.lineWrapWidth` characters, dynamically detect the terminal width with `os.get_terminal_size()` `os.get_terminal_size()` isnt implemented in py2, so `os.environ['COLUMNS']` can be read directly as a fallback if the...
Perhaps another shortcut parameter to `ic.configureOutput()`.
eg detect and pretty print ```python d = { ... } ic(d.keys()) ic(d.values()) ``` like ```python d = { ... } ic(list(d.keys())) ic(list(d.values())) ```
See https://github.com/gruns/ImmortalDB/issues/36.
Currently event handlers can only be setup at initialization time in the constructor's `options` parameter. Instead, `iFrameResizer` should implement the standard `EventTarget` interface * https://developer.mozilla.org/en-US/docs/Web/API/EventTarget with `addEventListener()`, `removeEventListener()`, and `dispatchEvent()`...