Skip to content

Making it easier to use unicode_literals #2536

Closed
@JukkaL

Description

@JukkaL

Currently using from __future__ import unicode_literals in Python 2 is kind of painful with mypy. Here are some potential issues:

  • Some typeshed stubs declare things to only accept str arguments, when in reality they also accept at least ascii-only unicode objects.
  • Mypy might not accept the implicit unicode literals in every context where a literal has a syntactic role (outside normal expressions), and b'foo' literals won't work in Python 3. String literal type escaping is an example.

It's fair to argue that using unicode_literals is a bad idea, but it's not uncommon to encounter real-world code using that, so getting mypy to work with it might be at least somewhat important.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions