You can subscribe to individual issues using RSS. That's the way I tend to
keep track of issues which are of particular interest to me.
-Phil
On 12/07/07, Peter Nixon < [EMAIL PROTECTED]> wrote:
>
>
> Hi Guys
>
> Am I just being dense, or is there no way in django's trac to monitor a
> bug
> for
Thanks for the commit Malcolm - seems you were right on my heels! And
James: will test on my own 2.3 install.
Thanks both.
-Phil
On 07/03/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 3/7/07, Phil Powell <[EMAIL PROTECTED]> wrote:
> > It renders a new Django in
I wouldn't normally post about an individual ticket to the list, but
this one is really biting me.
Ticket 3625 details an issue with the use of rsplit breaking syndb
with Python 2.3:
http://code.djangoproject.com/ticket/3625
It renders a new Django installation on Python 2.3 pretty unusable,
wh
A quick tip (which might be obvious, but might help a few people): I
use the RSS feed for specific tickets to keep track of their progress.
That way, if comments are added, or new patches are supplied, it
automatically pops up in "Django tickets" in my RSS reader.
-Phil
On 14/01/07, Adrian Holo
I'm just wondering if anyone is following up on this issue, as I've
just been bitten by it? Or I'd happy to pull together some diff's and
have a shot at some regression tests - but don't want to tread on
anyone's toes?
-Phil
On 01/12/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 1
On 14/06/06, oggie rob <[EMAIL PROTECTED]> wrote:
> So I think {% auto_escape_on %} or {% auto_escape_off %} are better
> options (depending on consensus to which should be the default).
I'm kind of +1 for leaving it off by default - I'm not keen on data
getting munged behind my back.
And as for
