Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3273868
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T18:58:38+00:00 2026-05-17T18:58:38+00:00

I am about to start ramping up on Django and develop a web app

  • 0

I am about to start ramping up on Django and develop a web app that I want to deploy on Google App Engine. I learn that Google has Django 0.96 already installed on the APP engine, but the latest “official” version of Django I see is at 1.2.3 and its a bit of an effort to install it there.

I am curious which version of Django is most widely used.

So, can you please guide me on which Django version I should ramp on and deploy based on the following criterion

  1. Stability and suitability for production release
  2. Availability for applications (or plugins) and which version is most supported by the community

Thanks a lot!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T18:58:39+00:00Added an answer on May 17, 2026 at 6:58 pm

    Most people are currently using Django 1.2. You should not use or learn Django .96 – it’s VERY old, and learning to use it won’t prepare you for any non-app-engine Django work since things have changed significantly since then.

    Django on App Engine is something of a pain, since you lose a lot of the ORM, which is a really nice reason to be working with Django. You also lose the ability to simply drop-in plugins and reusable apps that use any of the Django ORM. Anything with a models.py won’t work.

    Take a look at google-app-engine-django for help getting a more recent version running.

    http://code.google.com/p/google-app-engine-django/

    There is work to integrate the GAE storage engine into Django, and several projects have variously working implementations, but I wouldn’t expect really good ORM support for a while yet – 1.3 (which is still several months from release) will include hooks that make it easier to write NoSQL backends, but Django probably won’t ship with one.

    While there are security releases for old versions of Django, you should really be developing using the latest stable version. Major releases of Django have a very strong backwards compatibility promise, so going from 1.2 to 1.3 when it comes out will be pretty seamless.

    I strongly encourage you to think long and hard about what precisely App Engine offers your specific application before spending a lot of energy getting things working there. You lose application portability, scaling is still hard, and you don’t save money if your application gets popular. App Engine is not a forgiving introductory platform.

    For more conversation on this topic, take a look at this question:

    Why use Django on Google App Engine?

    particularly my answer there and the comments on it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am about to start writing a web app for the latest smartphones using
I'm about to start testing an intranet web application. Specifically, I've to determine the
I'm about to start a project that will record and edit audio files, and
I am about to start on a journey writing a windows forms application that
I am about to start a web project and have been working almost exclusively
I'm about to start a new django project with friends. This project includes a
I'm about to start a Database Design that will simply manage users under companies.
I'm about to start a fairly Ajax heavy feature in my company's application. What
I'm about to start on a large Qt application, which is made up of
I'm about to start a project for a customer who wants CMS-like functionality. They

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.