I never really liked how the templating system leaves all those
newlines. This middleware is cool, but it would really be nice if the
templating system could collapse the lines that only contain one or
more evaluating-to-nothing template tags.
Thoughts on a possible implementation:
What if an e
On Tue, 2006-08-01 at 09:02 +, favo wrote:
> I find a way to repeat this problems
>
> a snapshot of my apps' Directory Structure:
> \myapp\models\
> \myapp\models\__init__.py
> \myapp\models\category.py -- a model, manually specify app_label =
> "myapp" in Meta
> \myapp\urls.py -- import
seems we should find a way to let mod_python load all model first.
--~--~-~--~~~---~--~~
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
T
James Bennett wrote:
> The view decides which template to use, and what variables will be
> made available to the template, but that's not really the same thing;
> the question here is "which layer of Django decides what the actual
> output bits will be that go over the wire?" And the answer is m
(bump)
Just bumping this thread, since it seems to have gotten lost in the
OSCON excitement. I've also added an incomplete first draft of the docs
in question, at docs/multiple_database_support.txt.
JP
--~--~-~--~~~---~--~~
You received this message because you
Oh jeez, I just noticed the 'filesizeformat' filter...
Well, there's 5 minutes of my life I'll never get back :)
Jay P.
On 8/1/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> I just added a patch (http://code.djangoproject.com/ticket/2466) that
> adds a 'filesize' filter, which returns filesizes (f
I just added a patch (http://code.djangoproject.com/ticket/2466) that
adds a 'filesize' filter, which returns filesizes (from get_XXX_size)
in a human friendly way.
It's trivially simple, but I thought it might be useful to others.
Jay P.
--~--~-~--~~~---~--~~
Y
On Tue, Aug 01, 2006 at 07:58:10PM +0200, [EMAIL PROTECTED] wrote:
> I read a lot about django's auth system and the AUTHENTICATION_BACKENDS
> middelware. I also googled the following resources for LDAP support in django:
>
> http://code.djangoproject.com/wiki/MultipleAuthBackends
> http://www.jr
On 8/1/06, Kevin <[EMAIL PROTECTED]> wrote:
> Sure would be nice to save 5 characters every time I start the dev
> server
If you're that keen on saving 5 characters, go ahead and create a Bash
alias for "manage.py runserver hostname:8000". If you do that, heck,
you'd save *dozens* of characte
Hi all,
I read a lot about django's auth system and the AUTHENTICATION_BACKENDS
middelware. I also googled the following resources for LDAP support in django:
http://code.djangoproject.com/wiki/MultipleAuthBackends
http://www.jrandolph.com/blog/?p=22
http://www.carthage.edu/webdev/?p=12
Are th
I posted a test suite patch to demonstrate errors from the Ticket 526
(http://code.djangoproject.com/ticket/526).
To summarize:
When you have model with edit_inline=True *and* with unique_together
set, the only way that you can instantiate AddManipulator is that you
must have field with ed
+1 for this. I trade off between developing on my local network (but
not local machine) so I have to type:
runserver :8000
and over the internet where I have to type:
runserver :8000
Sure would be nice to save 5 characters every time I start the dev
server
--~--~-~--~~-
On 7/30/06, SmileyChris <[EMAIL PROTECTED]> wrote:
> 1. Technically, the view decides how a template is going to be
> displayed, not the template itself. Could the view, therefore, be the
> best place for escaping to happen?
The view decides which template to use, and what variables will be
made
I think that this is prone to error. At least for me, when I see a
piece of code like this one, I will definitly think that it needs to be
escaped:
{{ content }}
But if I'm passing something in the view code without escaping, I will
have to check the template to make sure it is being handled pro
On 8/1/06, favo <[EMAIL PROTECTED]> wrote:
> After updated to r3507,
> meets error when visit m2m field.
> AttributeError: 'ManyToManyRel' object has no attribute
> 'get_related_field'
Fixed in [3508].
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~-~--~~
Doug Van Horn wrote:
> Hopefully that makes the intent more clear.
Yes, much more clear! For some reason, I thought you were only
concerned with whitespace at the beginning and end of the response.
Sorry for the trouble!
Will.
--~--~-~--~~~---~--~~
You receive
On 8/1/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> When I try to log into Trac at the moment, I get a 500 error. Can
> somebody with access to the system have a look, please.
Fixed.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~-~--~~~---
On 1 Aug 2006, at 13:23, Michael van der Westhuizen wrote:
After updating SVN this morning I get the error below. Reverting to
revision 3506 resolves the problem.
The error occurs with the default site (no apps installed) - just
start a project, enable admin, syncdb, runserver, log in to admin,
After updated to r3507,
meets error when visit m2m field.
AttributeError: 'ManyToManyRel' object has no attribute
'get_related_field'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To pos
I find a way to repeat this problems
a snapshot of my apps' Directory Structure:
\myapp\models\
\myapp\models\__init__.py
\myapp\models\category.py -- a model, manually specify app_label =
"myapp" in Meta
\myapp\urls.py -- import category.py
in urls.py, if we import category.py then the app
20 matches
Mail list logo
