From 6d29bff85bf3d9141156a1183826d4a04d9245fd Mon Sep 17 00:00:00 2001 From: Raphael Nestler Date: Tue, 9 Aug 2022 15:13:40 +0200 Subject: Update Python versions in dev docs Also remove mentions of Python 2 workarounds, since they aren't applicable anymore. --- docs/dev.rst | 20 ++------------------ 1 file changed, 2 insertions(+), 18 deletions(-) (limited to 'docs') diff --git a/docs/dev.rst b/docs/dev.rst index 0ff033f..c362724 100644 --- a/docs/dev.rst +++ b/docs/dev.rst @@ -30,17 +30,8 @@ Python Versions At the moment the following Python versions should be supported: -* Python 2.7 -* Python 3.4 and up -* PyPy tracking 2.7 and 3.2 and up - -While PyPy does not currently support 3.3, it does support traditional -unicode literals which simplifies the entire situation tremendously. - -Documentation must build on Python 2, Python 3 support for the -documentation is an optional goal. Code examples in the docs preferably -are written in a style that makes them work on both 2.x and 3.x with -preference to the former. +* Python 3.6 and up +* PyPy 3.7 and up Unicode ------- @@ -48,16 +39,9 @@ Unicode Unicode is a big deal in Babel. Here is how the rules are set up: * internally everything is unicode that makes sense to have as unicode. - The exception to this rule are things which on Python 2 traditionally - have been bytes. For example file names on Python 2 should be treated - as bytes wherever possible. * Encode / decode at boundaries explicitly. Never assume an encoding in a way it cannot be overridden. utf-8 should be generally considered the default encoding. -* Dot not use ``unicode_literals``, instead use the ``u''`` string - syntax. The reason for this is that the former introduces countless - of unicode problems by accidentally upgrading strings to unicode which - should not be. (docstrings for instance). Dates and Timezones ------------------- -- cgit v1.2.1