Re: moving to django 1.2.1

One issue that bit me that has also been mentioned here in other threads: errors that were previously caught are now raised as errors. So technically it was wrong previously but functionally it only breaks on 1.2. I haven't found a good explanation / summary of what/why/ which errors it now affect

custom validation for an inline formset, howto?

I am trying to perform custom validation on an inline formset. The docs indicate that custom formset validation should go through a custom clean method: http://docs.djangoproject.com/en/1.1/topics/forms/formsets/#custom-formset-validation but the clean method doesn't get called for my instance o

Re: Debugging Django project using Eclipse (Apache + mod_wsgi)

this is a good place to get started: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques On Mar 16, 10:11 am, Stefan wrote: > Hello, > > When i used Django web-server there were no problems with debugging > Django projects in Eclipse IDE. > I had to deploy it on Apache web server. > > How

getting _collect_sub_objects() error during delete if a foriegn key's foreign key is null

Trying to delete objects from the django admin or app code, I'm getting an error: File "/home/styleseat/ssenv/lib/python2.6/site-packages/django/db/ models/base.py", line 595, in _collect_sub_objects sub_obj._collect_sub_objects(seen_objs, self, related.field.null) AttributeError: ‘NoneType’ obj