While dealing with http://code.djangoproject.com/ticket/2127, I
realized that unless your decorator takes the same number of arguments
as the filter function, it will fail since
FilterExpression.args_check() (in django/template/__init__.py) is using
inspect.getargspec() to count the number of requ
What's our policy on template filters failing? If applying a filter
raises an error, should we just trap it and return the empty string, or
raise an error? I can't find this written down anywhere, but maybe I've
missed it.
Should the answer depend upon the DEBUG setting?
This is in particular re
[EMAIL PROTECTED] wrote:
> perhaps we could put it all into backend/creation.py.
That's what i had, early, implemented with the firebird backend patch,
put the sequence and triggers sql in creation.py. And now i was trying
retain the management.py intact in terms of functionality, but your
aproa
Note that if anyone comments on the northern English town of
"Scunthorpe" it will get caught as a profanity! This has happened on
websites before (but not Django ones, this was a while ago).
One particularly strict profanity filter eliminated half the country
from registering on the site - anyone
hey Adrian I have another quick question i haven't been able to find
any indication of when 0.95 is going to be released on
djangoproject.com is it still going to be released, and if yes about
when.
Thanks a bunch
--~--~-~--~~~---~--~~
You received this message b
Just for information:
Now has a setting to keep it backwards compatible
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups
Hi!
Got a new patch for streaming uploads, in ticket #2070 enabling even
larger uploads and uploads in the admin.
If it is of any intrest.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
