Thursday, January 10, 2013

Re: Near term disadvantages of Django+Python 3 stack?


On Thu, Jan 10, 2013 at 9:47 PM, John <john.lehmann@gmail.com> wrote:
I understand that Django 1.5 RC supports Python 3, but for the sake of this question let's assume the 1.5 GA was already out.  As a developer, I want to use latest possible stable versions.  However, are there other implications for using a Py3 stack here?  For example, might I in the near future discover that 75% of the plugins which I might find useful will not yet be ported over for some time?  Are there any other gotchas that might make me want to stay with Python2.7 stack for a site I'll be building in a 6 month window?

You've pretty much identified the two biggest problems.

1) We've done plenty of testing under Python 3, but there's no testing like people actually using code in anger, so it's possible we will find small problems with our Python 3 implementation after 1.5 is finalised. If we find a particularly bad problem, we might be forced to break backwards compatibility for Python 3 projects.

2) The wider community of Django apps/plugins/libraries hasn't been updated for Python 3. You've said 75% - the number is probably closer to 95%. Of course, this is a great opportunity for you to become a huge community contributor by submitting pull requests for Python 3 updates.

Ultimately, the decision is yours. 

If you're completely new to Django, you have really tight deadlines, or you don't have a lot of confidence in the idea of diving into the internals of Django and 3rd party apps, it's probably better to stick with Python 2.7 for the moment. Without knowing you or your circumstance or experience level, I'd err on the side of caution and say this is the safer option.

However, if you're adventurous, you're not afraid of a few road bumps, and you're willing to do a bit of extra work to help port 3rd party projects, it would be a huge help to the Django community to see a live project working on Python 3; and long term, your code will be ready for the future.

Yours,
Russ Magee %-)

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate