将Google App Engine应用程序从Django 0.96迁移到Django 1.2 [英] Migrating a Google App Engine application from Django 0.96 to Django 1.2

问题描述

我将很快开始将我使用默认版本的Django（0.96）构建的不同的Google App Engine应用程序移植到Django 1.2中。我通常不使用任何特定的Django模块，除了i18n的东西可以翻译网站。

我打算通过 Django向后不兼容的更改从0.96到1.0 和不同的Django 发行说明。这些是现在的0.96和1.2之间的发行说明：

• 1.2发行
  
  
  
  • Django 1.2.5发行说明
  
  
  • Django 1.2.4发行说明
  
  
  • Django 1.2.2发行说明
  
  
  • Django 1.2发行说明
  
  


• 1.1发行
  
  
  
  • Django 1.1.4发行说明
  
  
  • Django 1.1.3发行说明
  
  
  • Django 1.1.2发行说明
  
  
  • Django 1.1发行说明
  
  


• 1.0发行
  
  
  
  • Django 1.0.2发行说明
  
  
  • Django 1.0.1发行说明
  
  
  • Django 1.0发行说明
  
  

我想知道是否有更好的方式进行这种迁移/升级，或者如果有人已经完成它将有一些有用的提示。我知道有很多阅读涉及，这不是我想阻止的，但更多的是得到指针来平滑这个过程。

我有不同的应用程序迁移，但将从简单/小应用程序开始，以获得

解决方案

而不是试图弄清Django 0.96和1.2之间的一切变化，我的建议是写一个测试套件来覆盖您的UI行为。您可以使用新的测试版框架对每个模板进行单元测试，或者使用像 Selenium 这样的完整的基于浏览器的集成测试。

一旦你进行了工作测试，只需更新Django，重新运行你的测试，看看什么休息。如果您有集成测试，还可以通过上传非默认版本。

I will soon start to port my different Google App Engine applications built with the default version of Django (0.96) to Django 1.2. I generally don't use any specific Django modules apart from the i18n stuff to get the websites translated.

I plan to go through the backwards-incompatible changes to Django from 0.96 to 1.0 and the different Django release notes. Those are the current release notes available between 0.96 and 1.2:

• 1.2 release
  • Django 1.2.5 release notes
  • Django 1.2.4 release notes
  • Django 1.2.2 release notes
  • Django 1.2 release notes
• 1.1 release
  • Django 1.1.4 release notes
  • Django 1.1.3 release notes
  • Django 1.1.2 release notes
  • Django 1.1 release notes
• 1.0 release
  • Django 1.0.2 release notes
  • Django 1.0.1 release notes
  • Django 1.0 release notes

I am wondering if there is a better way of doing this migration/upgrade, or if someone that has already done it would have some useful tips. I know there's a lot of reading involved, and that's not what I'm trying to prevent, but more to get pointers to smoothen this process.

I have different applications to migrate, but will start with a simple/small application to get the gist of it.

解决方案

Rather than trying to figure out everything that's changed between Django 0.96 and 1.2, my advice would be to write a test suite to cover your UI behavior. You can unit test each of your templates with the new testbed framework, or write full browser-based integration tests with something like Selenium.

Once you have working tests, just update Django, re-run your tests and see what breaks. If you have integration tests, you can also test your changes against production by uploading a non-default version.

这篇关于将Google App Engine应用程序从Django 0.96迁移到Django 1.2的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！