49 | | Do a subversion checkout of django trunk. Or get version 1.0 that has the signals speedup (ticket 6814) |
50 | | Or if ticket 6814 is not in yet, apply patch ticket 6857 (http://code.djangoproject.com/ticket/6857) |
| 49 | Do a subversion checkout of django trunk. |
| 50 | {{{ |
| 51 | svn co http://code.djangoproject.com/svn/django/trunk/ django-trunk |
| 52 | }}} |
| 53 | |
| 54 | Currently the #6814 ticket is not resolved, so you need to apply the patch from #6857 to make robustapply work. |
| 55 | Without the patch signals will blow up showing obscure import errors. |
| 56 | |
| 57 | Once Django 1.0 is out, it should run on PyPy out of the box. |
57 | | * elementtree (from xml.etree import cElementTree as ElementTree) |
58 | | python-openid |
59 | | yadis |
60 | | gdata |
61 | | |
62 | | * hashlib |
63 | | python-openid |
64 | | gravatar |
| 64 | Django only requires Python 2.3. So as such Django runs just fine on PyPy. |
| 65 | But, be aware that many popular django applications depend on Python 2.5 runtime lib. |
| 66 | |
| 67 | Getting the Pinax Django Hotclub project running we needed a couple of extra dependencies, |
| 68 | * elementtree |
| 69 | * hashlib |
| 70 | But these have now been included in PyPy during the EuroPython sprint (well done hpk & hruske). |
| 71 | |
| 72 | If you try to run Pinax on cPython 2.4 you would have this dependency problem. |
| 73 | |
| 74 | == Pinax Project == |
| 75 | |
| 76 | If you want to get the Pinax project up and running you need to check out the trunk |
| 77 | {{{ |
| 78 | svn checkout http://django-hotclub.googlecode.com/svn/trunk/ django-hotclub |
| 79 | }}} |
| 80 | This checks out pinax and all the associated applications from Google Code. If you want to check out with |
| 81 | git follow the instructions on the project wiki at |
| 82 | |
| 83 | http://code.google.com/p/django-hotclub/wiki/UsingGit |
| 84 | |
| 85 | |
| 86 | == Run Django == |