|Version 1 (modified by ymasuda, 10 years ago) (diff)|
Please feel free to share the things that tripped you up when you install Django.
django-admin.py does not work
-bash: django-admin.py: command not found
You don't have django-admin.py on your command search PATH.
Link <django_installation>/bin/django-admin.py to whereever on your PATH. Note that Python on most unix-like system uses /usr/local/lib/python2.X/site-packages/ for 3rd-party packages:
ln -s /usr/local/lib/python2.4/site-packages/django/bin/django-admin.py /usr/local/bin/django-admin.py
On unix-like system, django-admin.py says like: pkg_resources.DistributionNotFound: Django==0.91
You have two different versions of Django installed, and your django-admin.py does not point correct version.
Locate django-admin.py by which django-admin.py Unlink it and link correct django-admin.py from bin subdirectory of your django installation.
Using MySQLdb as DBI, it shows ImportError: cannot import name ImmutableSet .
You probably had MySQLdb 1.2.0 (or prior) installed, then override it to upgrade to 1.2.1.
MySQLdb versions prior than 1.2.0 have sets.py in MySQLdb installation. It does not contain ImmutableSet that is actually defined by built-in sets module in Python 2.4. If it left in your MySQLdb directory, it will be imported by somewhere in MySQLdb code in priority and cause ImportError.
Delete sets.py from your MySQLdb installation (only if you are sure using 1.2.1 or later).