Python 3.2 is a default python in Ububtu 12.04 LTS so I think Python 3.2 support is pretty important.
And what are the gains of having "u" prefixes all over the codebase? This makes the codebase less Python3-like. With PEP414-based code there must be explicit "b" and explicit "u" prefixes all over the code; the sweet unprefixed variant will be reserved for "naive strings" which are rarely useful. With unicode_literals explicit "b" prefix is needed if byte strings and explicit "str(foo)" call is needed for "native strings"; unicode strings are implicit and default in both Python 2.x code and Python 3.x code. This is more porting work but I think it is more rewarding because it leads to a cleaner code. среда, 22 августа 2012 г., 21:06:37 UTC+6 пользователь VernonCole написал: > > That seems to me (in my dark status as a lurker here) to be a brilliant > idea. > It is already established practice to say something like: "version 1.n of > django requires 2.m or later of Python". > The practice then would change to: "version 1.n of django requires 2.m of > Python or 3.3 or later". > I see from reading the text of PEP414 that there is an import hook > available to make this feature also work in Python 3.2. > Would there be any advantage to requiring support for older versions of > Python 3? I can't think of any. > Python 3.3 will be an established thing long before a django version using > it gains production status. We developers can use hooks and beta versions. > -- > Vernon Cole > > On Tuesday, August 21, 2012 4:03:57 PM UTC-6, DrMeers wrote: >> >> It's a shame we couldn't skip straight to Python 3.3 and take >> advantage of PEP414... >> >> On 22 August 2012 07:32, Adrian Holovaty <[email protected]> wrote: >> > On Tue, Aug 21, 2012 at 5:46 AM, Aymeric Augustin >> > <[email protected]> wrote: >> >> In my opinion, option (2) is a logical move at this point. However I >> >> believe it deserves a public discussion (or at least an explanation). >> >> What do you think? >> > >> > I prefer option 2 as well, because it seems like the Right Thing To >> > Do. Of course, there's no rush to do everything -- we can just nibble >> > off bits here and there. >> > >> > I'll have some free time soon and would be happy to help out migrating >> > code. (Relatively) mindless refactoring like this is one of my >> > favorite things to do. :-) >> > >> > Adrian >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Django developers" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> [email protected]. >> > For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> > >> > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/m94CZ4GZxLsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
