Thanks for the pro help John, I really appreciate it. On the other hand, I suppose I could find in the django source code and run it from there. (I ran the above whilst in my Webfaction's Django app directory.) Seems fine to me... With all that said, based on what you folks have been saying, I did run this command: ...
Great tip on using manage.py; I did not realize that they were the same thing. and that worked without error (I have "python" aliased to python2.7)! Also, just FYI (for my own future reference), I had some extra path information in my .bash_profile that was pointing to my Django projects's bin folder.
In this case, I do have available (my main project is there) but typically, don't you need to run startprojet before you have access to manage.py? I just removed the paths from my PYTHONPATH and reloaded my .bashrc file. Now, I'm back to not being able to run startproject via
Thanks so much for you time Sean and John, you guys ROCK!!!!! and are functionally identical, the difference is is bundled with the app and is an attempt at a global command, which does not work as well on our shared platform. Access denied for user 'my_username'@'localhost' (using password: YES)") django 1.3 admin problem How to syncdb from the XML-RPC API? Also, some prior experience with Django would be incredibly helpful, but not strictly necessary. If you're using pip to install packages (and I can't see why you wouldn't), you can get both virtualenv and virtualenvwrapper by simply installing the latter. Others think that since "this is a small project," that it's not necessary. None of the tools listed here will pay greater dividends then the use of a version control system. However, this project being in Python, Mercurial is a worthy Python based alternative. I'll be running on a 64-bit Arch server installation hosted by Linode, with whom I'm very happy. This is common, recommended practice among Python and Django users alike. It may sound unbelievable (considering the popularity of Git Hub), but developers have simply never been exposed to version control. If you don't head over to and find the install instructions for your architecture/os. For this reason, we'll be using virtualenv and the excellent extension virtualenvwrapper to manage our Django installation. Overwhelmingly, the ones having the most difficulty are those that do not use any form of version control.
One common problem with installing packages directly to your current site-packages area is that, if you have more than one project or use Python on your machine for things other than Django, you may run into dependency issues between your applications and the installed packages. I've consulted on a number of Django/Python projects and spoken to numerous developers in the last few years.
Instead, we'll use one managed by virtualenv that can't be messed up by other users (or yourself) working elsewhere on the machine. Before we actually start the project, we need to have a little talk.
Both are popular enough that learning resources abound online.
Make sure you have either git or Mercurial installed.
Both are almost certainly available via your distro's packaging system.
If you plan on using git, Git Hub is an obvious choice for keeping a remote repository.