On Sat, Apr 17, 2010 at 12:36 AM, Derek Hoy wrote:
>
> I'll dig around a bit more.
The problems seemed to come from the same models.py that was shared
across the projects. I moved a couple of imports and it seems fine
with trunk (r12996).
So it looks like it's the change in th
Strange, I had the same problem and rolling back to 12976 fixed it.
But another project still failed. It worked when I rolled back to
r12949.
http://code.djangoproject.com/changeset/12950 is the first of a few
that deal with app loading. It may be our projects had import errors
that weren't being
I sometimes return an 'error' string from my own tags when it's
important to see a problem.
One way of making that more elegant would be to make an explicit
MustNotBeSilencedException that a tag could use for error checking.
The template handling code would ignore all other exceptions.
Derek
-
Registry?
Derek
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL
On 9/18/06, Jeff Forcier <[EMAIL PROTECTED]> wrote:
>
> I've had excellent results with RimuHosting
+1
--
Derek
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
On 6/20/06, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> But it is an escaping issue.
Isn't the most common use case for this the problem of people entering
bad stuff into a form? In which case, regarding it as a validation
issue seems good to me.
For example, I used Webmin a few days ago to fix s
