I don't know if anyone will find this useful, but I thought I'd throw
it out there.
I wrote a little Middleware class to strip trailing and leading
whitespace from a response:
import re
class StripWhitespaceMiddleware:
"""
Strips leading and trailing whitespace from response content.
FWIWwebfaction has offered this for a while for python http://www.webfaction.com/freetrac BTW.. I can't see a reference to this on code.google.comOn 28/07/2006, at 12:53 PM, Tyson Tate wrote:I imagine there are some people here who (like me) want to open source some of their Django code, contrib
I imagine there are some people here who (like me) want to open
source some of their Django code, contrib apps, or other things but
cant run Subversion or Trac on their host. Google to the rescue, as
always:
http://code.google.com
Hopefully this can be useful to many of you.
-Tyson
On 7/27/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Make a setting to turn define the default, and if the setting's not
> there, auto-escape.
> Anyone that doesn't want it can just turn it off by defining the setting.
>
> AUTO_ESCAPE_TEXT = _True_|False
This is the exact scenario that should
On 28 Jul 2006, at 01:50, Ahmad Alhashemi wrote:
> Default escaping couples the Django templates with HTML. I don't think
> that this is a good idea, even if HTML is, incidentally, the most
> commonly used language in templates, for the time being.
Here's an idea I don't think anyone has
Default escaping couples the Django templates with HTML. I don't think
that this is a good idea, even if HTML is, incidentally, the most
commonly used language in templates, for the time being.
--~--~-~--~~~---~--~~
You received this message because you are
Tom Tobin wrote:
> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>> Adrian Holovaty wrote:
>>> There's no real reason, other than the fact that the core developers
>>> all use (and are happy with) the Subversion/development versions of
>>> Django, with which we've been enjoying the great changes to
Jeremy Dunck wrote:
> On 7/27/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
>> People run svn update at
>> different times and all that jazz. I know we've been burned once or
>> twice by people running different versions of django.
>
> Two-phase email? "I'd like to svn up, report back when
On Jul 27, 2006, at 3:22 PM, Simon Willison wrote:
> (Malcolm Tredinnick's patch looks like a really great bash at this;
> it's great that someone's taking the initiative and hammering out
> some code).
FYI, Malcom, Adrian and I spent some time talking this over today at
OSCON. Expect to see
On 27 Jul 2006, at 21:01, Tom Tobin wrote:
> From what I recall of conversations on the subject, default behavior
> will not be changed to auto-escape. Auto-escaping, under whatever
> proposal is accepted, will require some form of action to enable.
I like to think that's not set in stone yet.
On 7/27/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> perfect is what 1.0 is for.
I certainly hope this isn't the case. It'd kill me to see django get
caught up with the mythical 1.0 that seems to plague so many OSS
projects.
--
Kevin
--~--~-~--~~~---~--~~
You
On 28/07/2006, at 7:56 AM, Tyson Tate wrote:On 7/27/06, Ian Holsman <[EMAIL PROTECTED]> wrote: I for one would like a 0.95 release. ...Earlier today:On 7/27/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:... We're working on the .95 release as I typethis, though.Adrianyeah.. I saw that.but the
On 7/27/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> I for one would like a 0.95 release.
...
Earlier today:
On 7/27/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
...
> We're working on the .95 release as I type
> this, though.
>
> Adrian
--~--~-~--~~~---~--~~
I for one would like a 0.95 release.why?I think 0.95 is stable enough *as is*. sure it's not perfect, (thats what 0.96 is for ;-) but I would like people to stop using 0.91 ASAP.and personally I think trying to get a monthly release, or a release just before something major happens is a good
Regardless of the merits of the issue, it certainly doesn't help things
to get personal.
If you want to influence the process, stay cool and keep the emotional
attacks off the table.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Thanks again. :)
--~--~-~--~~~---~--~~
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
On Jul 27, 2006, at 3:57 PM, Matt Carter wrote:
> Unfortunately, "Matt the Destroyer" (me) is a completely different
> person than "simonslaw."
Indeed, turns out I was wrong.
Matt, I'm very sorry. I figured the odds of two people with the same
IP participating in the same thread was pretty
On Friday 28 July 2006 04:24, Simon Willison wrote:
> > ...
> > I've tested such a change on Django 0.95 - it seems to work OK.
>
> A neater way of doing that is to use the built-inr Python function
> callable():
>
> if callable(value):
> value = value()
>
> This seems like a neat addition
On 7/27/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Hi guys -
>
> This guy -- same guy, BTW -- has been banned. Apologies for letting
> him troll for so long.
>
> Jacob
A, and I was just about to introduce everyone to my little friend...
Jeremy Dunck wrote:
> On 7/27/06, Matt the Destroyer <[EMAIL PROTECTED]> wrote:
> > Does Django improve if everyone's out for lunch?
>
> I think that depends on whether we're all friends here. I certainly
> think about Django over lunch often.
GAYY!!!
BTW Jocab good one banning
Hi guys -
This guy -- same guy, BTW -- has been banned. Apologies for letting
him troll for so long.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
On 7/27/06, Matt the Destroyer <[EMAIL PROTECTED]> wrote:
> Does Django improve if everyone's out for lunch?
I think that depends on whether we're all friends here. I certainly
think about Django over lunch often.
--~--~-~--~~~---~--~~
You received this message
On Thursday 27 July 2006 18:48, Malcolm Tredinnick wrote:
> Aargh! Can you make a ticket with these details so that we don't lose
> them, please (I have flagged this email to look at later, too).
Sure. It's done as ticket #2438.
> This --
> the get_apps() and get_models() code -- is a slight
Tyson Tate wrote:
>
> [...] If you can't handle using an in-development framework that's
> improving by the hour [...] see it become the best web
> application framework in the world
> -Tyson
Very ambitious words there, Tyson. While I can agreeably forsee Django
eventually maturing into a
On 7/27/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Thursday 27 July 2006 19:47, Deryck Hodge wrote:
>
> > But how is remembering to do {! var !} any easier than remembering {{
> > var|escape }}? I think that's the issue most people had, that
> > escaping is easy to overlook.
>
> In my
On 7/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> When you talk all I hear is poop hitting a toilet.
...
> astablished
...
> use there nightly build it a production
> enviroment?
...
> last nights kernal build
...
> If you have ever worked on a non-kiddy project (ie $$$) you will
>
Todd O'Bryan wrote:
> On Jul 27, 2006, at 3:49 PM, [EMAIL PROTECTED] wrote:
>
> > Tom Tobin wrote:
> >> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> >
> >> In line with other sentiments I've expressed here in the past: IMHO,
> >> this means your *project manager* is addled, not Django's release
On 7/27/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Read about agile development. You can release stable code without
> freezing it.
I guess it depends on the definition of "stable." I agree that you
can have code that runs and runs well without freezing it. At some
point though, you gotta
Todd O'Bryan wrote:
> On Jul 27, 2006, at 3:49 PM, [EMAIL PROTECTED] wrote:
>
> > Tom Tobin wrote:
> >> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> >
> >> In line with other sentiments I've expressed here in the past: IMHO,
> >> this means your *project manager* is addled, not Django's release
On Jul 27, 2006, at 3:49 PM, [EMAIL PROTECTED] wrote:
> Tom Tobin wrote:
>> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
>> In line with other sentiments I've expressed here in the past: IMHO,
>> this means your *project manager* is addled, not Django's release
>> process. If you can understand
On 7/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Tom Tobin wrote:
> > On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
> > In line with other sentiments I've expressed here in the past: IMHO,
> > this means your *project manager* is addled, not Django's release
> > process. If you can
[EMAIL PROTECTED] wrote:
> Tom Tobin wrote:
> > On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
> > In line with other sentiments I've expressed here in the past: IMHO,
> > this means your *project manager* is addled, not Django's release
> > process. If you can understand that the development
Tom Tobin wrote:
> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> In line with other sentiments I've expressed here in the past: IMHO,
> this means your *project manager* is addled, not Django's release
> process. If you can understand that the development version is stable
> enough to use, but
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
>
> Tom Tobin wrote:
> > In line with other sentiments I've expressed here in the past: IMHO,
> > this means your *project manager* is addled, not Django's release
> > process. If you can understand that the development version is stable
> > enough to
On Jul 27, 2006, at 1:05 PM, Joe wrote:
> Malcolm Tredinnick wrote:
>> Release management is a little more faceted than that. You do
>> understand
>> that any Open Source project has multiple releases, right? Putting
>> out
>> periodic releases to act as checkpoints, regardless of whether it
On Thursday 27 July 2006 19:47, Deryck Hodge wrote:
> But how is remembering to do {! var !} any easier than remembering {{
> var|escape }}? I think that's the issue most people had, that
> escaping is easy to overlook.
In my proposal, if you do {{ var }} you are covered, so you don't have
to
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
> Adrian Holovaty wrote:
> >
> > There's no real reason, other than the fact that the core developers
> > all use (and are happy with) the Subversion/development versions of
> > Django, with which we've been enjoying the great changes to Django
> >
On 7/27/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Two-phase email? "I'd like to svn up, report back when ready."
>
> Or, if too large a team, cron'd switchtower/capistrano task?
Heh, I'm not saying it's not doable. It is a pain in the neck though,
and is alleviated by a point release. I
On 7/27/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
> People run svn update at
> different times and all that jazz. I know we've been burned once or
> twice by people running different versions of django.
Two-phase email? "I'd like to svn up, report back when ready."
Or, if too large a team,
On 7/27/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> Unless I missed something, the default escaping proposal hasn't been
> committed. And I've had an idea that I don't think came up, that I
> thought was perhaps worth throwing into the mix.
>
> Basically, {{ }} does escaping automatically,
Unless I missed something, the default escaping proposal hasn't been
committed. And I've had an idea that I don't think came up, that I
thought was perhaps worth throwing into the mix.
Basically, {{ }} does escaping automatically, and {! !} doesn't.
Of course, we can then argue about
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> I wonder, then, why .95 has been held off so long.
Hey Joe,
There's no real reason, other than the fact that the core developers
all use (and are happy with) the Subversion/development versions of
Django, with which we've been enjoying the great
Malcolm Tredinnick wrote:
> Release management is a little more faceted than that. You do understand
> that any Open Source project has multiple releases, right? Putting out
> periodic releases to act as checkpoints, regardless of whether it is the
> ultimate, be-all-and-end-all release has
On 7/26/06, monkeynut <[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/2433
> .. hopefully I didn't miss anything, I've been out in the sun all day.
Good stuff, Pete! I've committed that patch.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
On Thu, 2006-07-27 at 08:36 -0700, Tyson Tate wrote:
> It'd be nice if .95 would take care of at least *some* of the bugs
> that have been piling up in Trac. I understand the few who have commit
> access are insanely busy, but I just can't fathom a .95 release with
> the current state of trunk.
It'd be nice if .95 would take care of at least *some* of the bugs
that have been piling up in Trac. I understand the few who have commit
access are insanely busy, but I just can't fathom a .95 release with
the current state of trunk. (Whatever happened to the bug-fix sprint?)
It's a little
Joe wrote:
> I saw this post, but I wasn't sure a consensus had been reached.
I thought simonslaw summed it up pretty nicely.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
Do you know if something equivalent to the "DTM Migration Kit" you
mentioned exists as open software? Using a commercial product is not
very practical in my case, because the clients would have to agree on
buying it, which I belive is not likely.
I saw this post, but I wasn't sure a consensus had been reached.
--~--~-~--~~~---~--~~
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
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> How would the community around here feel about a beta/pre-release .95
> version?
>
Adrian mentioned doing one at OSCON. See this thread:
http://groups.google.com/group/django-developers/browse_thread/thread/75c0a1d3703ab81/
Cheers,
deryck
--
I'm new to Django, so forgive me if this idea walks all over the thus
far tidy architecture. I was wondering if db/models/query.py could
check for the type of the value in the parse_lookup() kwarg,value
pairs. If a value's type is FunctionType, the function could be
invoked. This would allow
51 matches
Mail list logo
