Opened 17 years ago

Last modified 16 years ago

#6695 closed

how to install: site-packages not where the document says it is on OS X — at Initial Version

Reported by: Michael S. Owned by: nobody
Component: Documentation Version: 0.96
Severity: Keywords:
Cc: mjs@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The following two paragraphs are included in an effort to get past the spam filter:

If you just want to experiment with Django, skip ahead to the next section; Django includes a lightweight web server you can use for testing, so you won’t need to set up Apache until you’re ready to deploy Django in production.

If you want to use Django on a production site, use Apache with mod_python. mod_python is similar to mod_perl — it embeds Python within Apache and loads Python code into memory when the server starts. Code stays in memory throughout the life of an Apache process, which leads to significant performance gains over other server arrangements. Make sure you have Apache installed, with the mod_python module activated. Django requires Apache 2.x and mod_python 3.x

The how to install documentation at:

h ttp://www.djangoproject.co m/documentation/install/

(URL broken in an attempt to get past the spam filter)

says that if django is installed via "setup.py install" django will be installed as a django subdirectory of the site-packages directory. It further suggests that to find the site-packages directory, one should run the following command:

python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"

However, this seems to produce the wrong output on OS X 10.5: the output it gives is:

$ python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"
/Library/Python/2.5/site-packages

but the actual directory django was installed in is:

/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages

(and this isn't a symlink to the other.)

More text in an effort to get past the spam filter:

If you plan to use Django’s manage.py syncdb command to automatically create database tables for your models, you’ll need to ensure that Django has permission to create and alter tables in the database you’re using; if you plan to manually create the tables, you can simply grant Django SELECT, INSERT, UPDATE and DELETE permissions. On some databases, Django will need ALTER TABLE privileges during syncdb but won’t issue ALTER TABLE statements on a table once syncdb has created it.

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top