On Nov 18, 4:40 pm, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote:
> Out of curiosity, for those who want RequestContext added to
> render_to_response, is there a reason you don't like using
> direct_to_template instead?
Holy smokes, that thought never crossed my mind, despite using both
the dire
On Sep 27, 9:41 pm, yish <[EMAIL PROTECTED]> wrote:
> I defined my search_fields for my model as
> seach_fields ('name')
> instead of
> search_fields ['name']
> ...
> If anyone is curious, what ended up happening is instead of iterating
> across the search fields, it iterated across the letter
On Apr 5, 5:25 am, "Yann VR" <[EMAIL PROTECTED]> wrote:
> I just wanted to bring attention to the
> tickethttp://code.djangoproject.com/ticket/3075
It looks like Adrian approves:
http://code.djangoproject.com/ticket/3075#comment:6
Used like so, the intent is clear:
{% ifequal a x and b y %}
{%
On Mar 27, 7:25 am, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> Wouldn't you know it I have a very good book on svn (the pragmatic one) but
> it's in New Zealand and I'm in Indonesia! Doh!
There's also the great and free SVN Book available on the web:
http://svnbook.red-bean.com/
Hope this helps,
Lachlan Cannon wrote:
> It feels right to me to have admin and the model separate. The way I think of
> it
> is this: Suppose I distribute an app and a user decides to use the app, but
> doesn't run the auto-admin. With my admin information factored out in a
> separate
> file: admin.py, she's no
Adrian Holovaty wrote:
> I'd like to take the clean route and move the admin definitions into a
> separate file, or at least still in the models.py but not within the
> models themselves. Of course, that's not as convenient as defining the
> admin stuff directly within the model, but another solut
sbain wrote:
> How would one now recommend that a new Windows developer install Django
> in a such a way as to facilitate keeping his Django updated to the
> trunk?
I only dabble with Django from time to time, but here is how I have it
set up (the following assumes C:\Python24\ as the root):
1.
No problem, I did the easy part. Figuring out where the tests go was
a lot easier that actually adding the new syntax to the template
system, I'm sure.
I just hope this helps the new syntax get added. I really think it
would be an important addition to the template system.
Will.
On 9/13/06,
Hawkeye wrote:
> if someone else has time to
> write a few tests, I'd be appreciative.
I have the time! I added a new patch that includes tests:
http://code.djangoproject.com/ticket/648
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
Ian Holsman wrote:
> I would be +1 on this if it included the site domain in the user-agent.
> having it this way will just cause wikipedia to block it when a
> single badly behaving django-bot uses it.
+1 on including the domain in the User Agent... good idea.
--~--~-~--~~-
Adrian Holovaty wrote:
> Sounds pretty good to me. Let's do it.
I opened a ticket and submitted a patch:
http://code.djangoproject.com/ticket/2482
My patch adds a keyword arguement to the 'values' method, as originally
proposed. It could be adapted pretty easily to Gary's suggestion of a
separa
Gary Wilson wrote:
> In other words, leave lines that I add, but remove the empty lines that
> had template tags on them.
+1
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
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
Doug Van Horn wrote:
> I wrote a little Middleware class to strip trailing and leading
> whitespace from a response:
I may be misunderstanding something, but doesn't your middleware
actually leave whitespace at the beginning and end of the response?
If response.content = '\n\n\nHello.\n\n' it is
14 matches
Mail list logo
