On 8/25/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 8/25/05, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > OK, it's back. Must've been the broken sql connection Adrian
> > explained earlier.. just no error message this time.
>
> Jacob was upgrading Trac, so we no longer get those databa
On 8/25/05, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> OK, it's back. Must've been the broken sql connection Adrian
> explained earlier.. just no error message this time.
Jacob was upgrading Trac, so we no longer get those database errors.
We apologize for the short downtime!
Adrian
--
Adrian
OK, it's back. Must've been the broken sql connection Adrian
explained earlier.. just no error message this time.
On 8/25/05, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Just in the last few minutes, it seems that Trac is no longer talking to svn.
>
> For example, this page doesn't show any timel
Just in the last few minutes, it seems that Trac is no longer talking to svn.
For example, this page doesn't show any timeline info:
http://code.djangoproject.com/timeline/
Whereas a few minutes ago, it showed the changeset for ticket 122.
On 8/25/05, Milton Waddams <[EMAIL PROTECTED]> wrote:
> It wouldn't work for me tb below, the admin for Site
> (/usr/lib/python2.3/site-packages/django/models/core.py) needed to be
> indented.
core.Site doesn't *have* an admin in the standard Django distribution,
so that's something you must've a
It wouldn't work for me tb below, the admin for Site
(/usr/lib/python2.3/site-packages/django/models/core.py) needed to be
indented.
Unhandled exception in thread started by
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/django/core/management.py",
line 560, in inner
All,
By popular demand, I'm about to change Django's model syntax to use
"fieldname = FieldClass" instead of "FieldClass('fieldname')". This
has been a longstanding ticket --
http://code.djangoproject.com/ticket/122.
This change is BACKWARDS-INCOMPATIBLE, so don't "svn update" your code
until yo
I'm rewriting a Rails application in Django, and thusfar it's been a
pleasant process. However, I'm having a conceptual block on how to
solve a problem "the Django way."
My application has essentially three types of objects that users will
view (lets call them Foo, Bar, and Baz), and each of tho
