Sebastian Pipping

Thanks for the pointer to `egencache`. I am unsure how to best improve the situation so the the next person will not have to find this ticket or open a...

Confirming as a bug, image `node:4-alpine` is running Python **2.7**.14 which does not understand type annotations used by Python >=3 and pip >=21.

Can this be closed as obsolete?

You're considering to add support of user controlled format strings, right? I would like to point out potential security implications, e.g. when using `.format`: http://lucumr.pocoo.org/2016/12/29/careful-with-str-format/.

Hi! I don't have Windows at hand to try this out easily. Could you point me to the authoritative documentation on these kinds of Network paths?

Before I get to take a closer look to confirm or not confirm this as a bug, let me share this shell output: ```console # ./uriparse http: uri: http: scheme:...

I guess I can acknowledge `absolutePath` as a suboptimal design but I'm tending towards: bad design, not a bug (that we could fix (without breaking ABI and making things worse)).

Could be more fun, agreed. Without breaking ABI (or even API), we cannot do anything about it, right?

I found this comment block from 55ea6ab4e6bc112498dd1a0141915856b7965f75 in the test suite: > ``` > ============================================================================ > Rule | Example | hostSet | absPath | emptySeg > ------------------------------------|---------|---------|---------|--------- > 1) URI...

Hi @yescallop, thanks for bringing this to my attention. From a quick look all three of these are bugs. I will have a closer look.