Hi
There are a number of place in the django codebase that trap Exception
and then raise a new exception but only convert the original exception
to a string to indicate what went wrong. Its often necessary to see the
full traceback of the original exception to work out whats going wrong.
The one
e
> missed the mark on this.. I'm relatively new to django-dev
> discussions.
>
>
> -justin
>
>
>
>
> On Fri, Feb 22, 2008 at 6:16 AM, Graham Carlyle
> <[EMAIL PROTECTED]> wrote:
>
> I'd like to request that FilePathField
I'd like to request that FilePathField should have an extra option that
causes it to only save a relative path (to the path parameter), say
called "relative".
Having an absolute path stored makes it harder to move data between
machines that are set up differently (say development and production)
Hello,
No-ones responded to my initial email. So is this the wrong place to
raise this request? Should I have posted to django-users? Should I raise
a ticket for this?
thanks,
Graham
On Tue, 2007-09-04 at 15:25 +0100, Graham Carlyle wrote:
> Any chance the pre_save & post_save signa
Any chance the pre_save & post_save signals sent by the
django.db.base.models.Model.save could have the raw flag passed as an
additional parameter to them?
My app uses theses signals to apply some common post save functionality
to a bunch of models. But loading fixtures causes problems as my app'
