MacPorts fragments a normal Python installation up into multiple smaller packages. For example: The sqlite3 support which is actually part of the core Python package is there in py25-sqlite3. But if you've already uninstalled MacPorts this is moot now, except if you want to reinstall it to get things like PostgreSQL and MySQL.
I have never tried getting Django to work with the version of Python that is bundled with MacOSX 10.5.x but it should normally work out of the box. > > I uninstalled Macports and removed all the django files I could find, then ran setup.py install "manually" but no luck. > What error did you get then? -- Horst On Fri, Nov 28, 2008 at 7:38 AM, jconway <[EMAIL PROTECTED]> wrote: > Horst & Malcolm > > Thank you for your suggestions, they helped me determine that the > problem is machine specific. > > On Nov 27, 3:03 am, "Horst Gutmann" <[EMAIL PROTECTED]> wrote: > >> Are you sure, that your django installation is complete? Esp.: Do you >> have a db/backends/dummy/base.py and a db/backends/dummy/__init__.py >> in >> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/s >> ite-packages/django/ > > Yes, these files are in these locations and are not damaged as far as > I can tell. > > On Nov 27, 8:11 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: > >> Also, if you're just starting out with Django, why are you setting >> DATABASE_ENGINE='dummy'? It's not one of the database backends that we >> document or suggest for use. Mostly there for historical reasons. > > I didn't set anything for the DATABASE_ENGINE, it was empty. I was > going thru the tutorial and made it to the section called "The > development server". At that point I had not touched the settings.py. > After your message above I opened the settings.py and made sqlite3 the > DATABASE_ENGINE. I tested and got essentially the same error initially > reported except the last line said something about no module named > _sqlite3. > > On the computer with the problems noted above I had installed django > using Macports (I installed Macports specifically for this django > install) I uninstalled Macports and removed all the django files I > could find, then ran setup.py install "manually" but no luck. > > I went to another computer with just the default mac os x 10.5.5 > installed and was able to install a fully functional version of django > in about 10 minutes (manually, instead of using Macports).So, for my > purposes, I consider this problem solved. (although if anyone has any > ideas that will save me from doing a clean system install on my > primary computer just to get django running on it, I'm open to > suggestions) > > thank you for your help > > james > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
