Django Development Version On Windows

Written by Martin Geber on December 1, 2007 at 6:38 p.m. Filed unter: Django. 1 Comment. Trackback URL.

TortoiseSVN

I work with the Django development version on my (linux) server. But I work with a Windows Operation System, which is very dump when it comes to SVN Checkouts. There are some solutions for the command line. Hey, honestly the windows command line is annoying, isn't it?

TortoiseSVN

TortoiseSVN is a very easy to use tool for windows, which enables you to download the current Django Development Version.

Installing TortoiseSVN

Go to the TortoiseSVN Download page and select the MSI-file, which fits your windows.

Installing is very easy:

Click "Next >" twice
Deselect "Additionally Icon set", "..(GB)..", "..(US).." by clicking the storage and clicking than "Entire feature will be unavailable" (This saves performance and keeps your disc free.)
Confirm with "Next >" and install by clicking "Install"
"Finish"
Restart your PC

Creating a Django SVN Checkout

Go to your site-packages folder (commonly C:\Python2.X\Lib\site-packages). In this folder you create a folder called django. Right click in this folder and select "SVN Checkout". Use this URL http://code.djangoproject.com/svn/django/trunk/django/.

Congratulations! You're done.

Updating the Django Development Version

Move again to the site-packages folder and right click on django, there you can select "SVN Update".

That's it.

Comments

The comments also include all Trackbacks.

Moof commented, on December 8, 2007 at 2:38 p.m.:

I do something slightly more complex:

First I install django on my boxes, mostly to get the scripts set up in the right directories, but if you have other ways of doing that or it's not important to you, then that's up to you.

I have a subversion repository called "DjangoDir". In it, I have a bunch of svn:externals references to the application packages of all my applications, as well as any external ones I happen to use, such as django_evolution. I don't use a layout like you propose in your freelancer post, but it's a similar idea. I also include the "django" package of django trunk.

I check this out on my linux server, and on a directory in "My Documents" on my windows dev system. This means I have an exact mirror on both, up to the last svn update.

The final step is to go to C:\Python25\lib\site-pacakges (or wherever your site packages are) and add a "django.pth" file (or edit an existing one if you use setuptools), which has inside of it just the full path to your DjangoDir working copy. Make sure you remove any "django" directories that are hanging about from your django installation.

As of now, both django, and all your django apps, are on the standard python path. You can work as normal inside your application directories, and tortoisesvn will just check in and out to your application repository. Once a day I go to my root DjangoDir, and do a svn update, which will go through all my apps, including django, and pull in all the latest updates.

Martin Geber