Skip to content

Remove no-op __future__ imports, Unicode strings#362

Open
DavidCain wants to merge 2 commits intojrief:masterfrom
DavidCain:drop-unicode-literal-import
Open

Remove no-op __future__ imports, Unicode strings#362
DavidCain wants to merge 2 commits intojrief:masterfrom
DavidCain:drop-unicode-literal-import

Conversation

@DavidCain
Copy link
Contributor

Version 2.3 officially dropped support for Python 2.7 (which reached its end of life at the end of 2020).

In Python 3, all string literals are Unicode.

Expressly stating file encoding (with # -*- coding: utf-8 -*-) is no longer necessary (files now default to being interpreted as UTF-8 instead of ASCII), but it's somewhat harmless.

Version 2.3 officially dropped support for Python 2.7 (which reached its
end of life at the end of 2020).

In Python 3, all string literals are Unicode.

Expressly stating file encoding is no longer necessary (files now
default to being interpreted as UTF-8 instead of ASCII), but it's
somewhat harmless.
In Python 2, strings which made use of Unicode characters would be
prefixed with `u`. In Python 3, this prefix is a no-op. We can safely
remove it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant