Something else just crossed my mind as well. The issue, AFAIK, is that older versions of Ubuntu / Python 2.5 stored third-party libraries (e.g. stuff you easy_install) in /usr/lib/python2.5/site-packages. With the upgrade to Ubuntu 9.04 / Python 2.6, these packages are now stored in /usr/lib/python2.6/dist-packages. Note that the old site- packages path is missing from your PythonPath. It's not just as simple as adding the old site-packages directory to your python path though. The compiled pyc files (and possibly other things) in that directory are specific to the version they were compiled with and will likely cause more headaches.
If Deportista is a third-party library that you used setup.py or easy_install to install, you might just want to try re-installing it using the same method. If, on the other hand, Deportista is something you manually plunked down into the site-packages dir (or symlinked into), then you'll just manually have to move it to some other directory in your Python path (e.g. /usr/lib/python2.6/dist-packages). Make sure to remove all the old pyc files in there though! -- Andrew On Jul 7, 9:10 am, Andrew Fong <fongand...@gmail.com> wrote: > Don't know if you tried this already, but the Ubuntu 9.04 Release > Notes mention something about this: > > http://www.ubuntu.com/getubuntu/releasenotes/904#python%20ImportError... > > """ > A bug in the python packages present in jaunty prior to the Ubuntu > 9.04 release candidate caused python modules to fail to be registered > for use with the current python version, python 2.6. This problem > appears as an import error, e.g: > > ImportError: No module named foo > even though the package providing the module package is installed. > > To correct this, run the command: > > sudo dpkg-reconfigure python-foo > for each python-foo package providing an affected module. > > """ > > -- Andrew > > On Jul 7, 7:43 am, Miguel <migue...@gmail.com> wrote: > > > > > Thank you Aaron. I will try to follow your pieces of advices. Fortunately it > > is not my production enviroment. > > > Miguel > > > On Thu, Jul 2, 2009 at 12:47 AM, Aaron Maxwell <a...@redsymbol.net> wrote: > > > > Hm. It involves this module Deportista. I haven't heard of it, so I'm > > > assuming it's either a third-party library you are using, or one a module > > > made in house. > > > > You might try this: (assuming unixy environment) > > > > 1) At a shell prompt, set PYTHONPATH to the value you included in the > > > attached > > > error report page. (you know how to do this? If not, look up setting and > > > exporting environment variables.) > > > 2) Also set DJANGO_SETTINGS_MODULE > > > 3) Start a python interpreter > > > 4) type in "import entrenatech.views" > > > > Does this reproduce the Deportista importerror? If so, that is a good > > > clue. > > > > On Wednesday 01 July 2009 12:55:05 am Miguel wrote: > > > > The error is: > > > > ViewDoesNotExist at / Could not import entrenatech.views. Error was: No > > > > module named Deportista > > > > As you said, Django .96 might be incompatible somehow, but I have to > > > > keep > > > > it becasuse it is a little messy to updgrade the django version. Too > > > > much > > > > production code. > > > > -- > > > Aaron Maxwell > > >http://redsymbol.net/ --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
