I like the idea of getting a full stack trace using python 2.5 I don't know what you platform is, but at least on linux (and similar systems) you can easily install multiple versions of python without causing trouble*. You grab the sources, do a make, and then, instead of doing make install, you do make altinstall. Then "python" still refers to your original version, but your additional version is available as, say "python2.5". Then use virtualenv to make an environment for django tied to python2.5, and do a checkout/clone/ whatever (assuming that your project is under revision control) of your project into the virtual environment (saves trouble with wrong version .pyc files). Activate the virutal environment, pip install django and your requirements, and fire up manage.py runserver. The whole process shouldn't take more than an hour if you know what you're doing, or a couple of hours if you need to read a bunch of documentation.
[ * I've got 2.4 (for zope/plone), 2.5, 2.6, 2.7, 3.0, and 3.1 on my laptop. ] Bill On Fri, Apr 16, 2010 at 2:29 AM, zayatzz <alan.kesselm...@gmail.com> wrote: > Okay. I will try to test it in the way suggested by Bill and Karen. > > This will take me some time though. Hopefully you will be able to keep > track of this thread even though it will get pushed to later pages > when new threads are created. > > Alan > > On Apr 15, 10:52 pm, Karen Tracey <kmtra...@gmail.com> wrote: >> On Thu, Apr 15, 2010 at 3:48 PM, Bill Freeman <ke1g...@gmail.com> wrote: >> > Sadly, the problem string doesn't occur at the top level of any of those >> > local >> > vars. It was worth a shot. It's probably in the context. >> >> > If I were you, I'd go find the raise wrapped... in debug.py down at the >> > bottom >> > of the stack trace, and stick a pdb.set_trace() there. Then (assuming you >> > do this under manage.py runserver) you can poke around to see what was >> > being rendered and what's in the context. The exception being wrapped may >> > have useful information that isn't showing in the stacktrace. If you can >> > find >> > the actuall line of code that is getting the exception, you may be >> > able to figure >> > out why it thinks it has to convert something to ascii (which is probably >> > the >> > default string encoding, use sys.getdefaultencoding() to find out). >> > Probably >> > something is applying str() to a unicode object. >> >> > I'm sorry that I can't provide a shortcut. Perhaps someone else will. >> >> If there is a way to run the app using Python 2.5 instead of 2.6 then the >> debug information would include the original traceback. Alternatively if it >> could be run with a recent checkout of either the 1.1.X branch or trunk then >> the full traceback would appearing, instead of it getting cut off at "raise >> wrapped". >> >> Karen > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@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. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
