Rob Speer writes:
> There is one more difference I have found between Python's encodings and
> WHATWG's. In Python's codepage 1255, b'\xca' is undefined. In WHATWG's, it
> maps to U+05BA HEBREW POINT HOLAM HASER FOR VAV. I haven't tracked down
> what the Unicode Consortium has to say about thi
On 2018-01-12 06:10 AM, Stephen J. Turnbull wrote:
Rob Speer writes:
> There is one more difference I have found between Python's encodings and
> WHATWG's. In Python's codepage 1255, b'\xca' is undefined. In WHATWG's, it
> maps to U+05BA HEBREW POINT HOLAM HASER FOR VAV. I haven't tracke
On Fri, Jan 12, 2018, at 03:10, Stephen J. Turnbull wrote:
> > Other than that, all the differences are adding the fall-throughs in the
> > range U+0080 to U+009F. For example, elsewhere in windows-1255, the byte
> > b'\xff' is undefined, and it remains undefined in WHATWG's mapping.
>
> I real
On Thu, Jan 11, 2018, at 17:41, Victor Stinner wrote:
> I like the idea of having a fully qualified name that "works" (can be
> resolved).
>
> I don't think that repr() should change, right?
What if we made these types available under their current name in the types
module? e.g. types.module, ty
On Thu, Jan 11, 2018 at 8:45 PM, Steve Dower wrote:
> I certainly have code that joins __module__ with __name__ to create a
> fully-qualified name (with special handling for those builtins that are not
> in builtins), and IIUC __qualname__ doesn't normally include the module
> name either (it's i
