Django devs,
I've noticed that the new ALLOWED_HOSTS causes the site
to return HTTP-500 errors whenever a user submits a request with an
HTTP_HOST header that is not allowed. This is flooding my developers'
inboxes with spurious error messages. The site is refusing the
requests as expected, but
On Sat, 2009-05-30 at 16:47 -0400, J. Clifford Dyer wrote:
> At the moment, admindocs raises an unhandled KeyError when trying to
> display documentation on custom field types, because it tries to pull a
> human readable field type description out of a dictionary, based on the
> return value of th
On Wed, 2009-05-13 at 17:20 -0400, J. Cliff Dyer wrote:
> On Wed, 2009-05-13 at 15:31 -0400, J. Cliff Dyer wrote:
> > On Wed, 2009-05-13 at 14:40 -0400, J. Cliff Dyer wrote:
>
> > > [...] but it occurs to me that if through=MyModel is set on the
> > > ManyToMany
On Wed, 2009-05-13 at 15:31 -0400, J. Cliff Dyer wrote:
> On Wed, 2009-05-13 at 14:40 -0400, J. Cliff Dyer wrote:
> > [...] but it occurs to me that if through=MyModel is set on the
> > ManyToMany, the sequence on MyModel will already be handled by the loop
> > at line 112
On Wed, 2009-05-13 at 14:40 -0400, J. Cliff Dyer wrote:
> On Wed, 2009-05-13 at 12:49 -0400, J. Cliff Dyer wrote:
> > Setup:
> >
> > Ubuntu 9.04
> > Python 2.6.2
> > Django 1.0.2
> > Postgres 8.3.7
> > postgresql-psycopg2
> >
> > I'
On Wed, 2009-05-13 at 12:49 -0400, J. Cliff Dyer wrote:
> Setup:
>
> Ubuntu 9.04
> Python 2.6.2
> Django 1.0.2
> Postgres 8.3.7
> postgresql-psycopg2
>
> I'm having issues using ./manage.py syncdb and ./manage.py flush with a
> project of mine. I
Setup:
Ubuntu 9.04
Python 2.6.2
Django 1.0.2
Postgres 8.3.7
postgresql-psycopg2
I'm having issues using ./manage.py syncdb and ./manage.py flush with a
project of mine. I've got an app, venues, which defines a
ManyToManyField.
After syncdb loads the fixtures, (and only if it tries to load fixt
+1
I think Warren's suggestion is the clearest. I also like the "core
developers" bit, but I would put that in as a second sentence.
Something like:
"""
Discussion group for issues regarding the development of the Django
framework itself. This is primarily for core developers. For
discussion
On Mon, 2008-12-15 at 09:12 -0500, Karen Tracey wrote:
> I'd think it unlikely at this point a change would be made that would
> prohibit having a field named 'objects'; the time for such a
> backwards-incompatible change was pre 1.0, if ever. If no one pre-1.0
> found the exisitng behavior troub
I was hesitant on this when I heard rumblings of it around 1.0, but my
workplace is finally getting off RHEL 4, which had Py 2.3, so I no
longer have an issue with dropping 2.3 support. RHEL 5 is at 2.4. Are
other places are still stuck with RHEL 4?
Even before, the install notes for contrib.gi
I like the new new version much better.
With the old new one, I kept going through the search bar, and contrary
to David Cramer's opinion, I like being able to drill town to what I'm
looking for (as long as it's not frustrating trying to find it). It
gives me the sense that I know where I am, an
Apologies for posting before I finished reading.
On Mon, 2008-06-09 at 15:28 -0500, James Bennett wrote:
> On Mon, Jun 9, 2008 at 2:47 PM, J. Cliff Dyer <[EMAIL PROTECTED]> wrote:
> > I agree with the sentiment of this, but we've passed the point where
> > it'
On Mon, 2008-06-09 at 15:28 -0500, James Bennett wrote:
> On Mon, Jun 9, 2008 at 2:47 PM, J. Cliff Dyer <[EMAIL PROTECTED]>
> wrote:
> > I agree with the sentiment of this, but we've passed the point where
> > it's a useful argument.
>
> I'll c
On Mon, 2008-06-09 at 14:08 -0500, James Bennett wrote:
> There would be frustration from people who want to stick to, say, the
> hypothetical 0.98 but need a third-party app that forges ahead to the
> hypothetical 0.99. There would be gnashing of teeth from people who
> would hear that they need
On Sat, 2008-06-07 at 12:06 -0700, Jacob Kaplan-Moss wrote:
> For the record, and if the author of this blog post is reading: I
> can't stand the passive-aggressiveness of making a rant on your blog
> and waiting for us to read it. I wish this had been brought up here
> instead of trying to drum
See ticket #6095 in trac. The fix is on its way.
Cheers,
Cliff
On Mon, 2008-05-19 at 06:53 -0700, JReynolds wrote:
> I posted this on django-users before and didn't get much response, so
> asking here...
>
> I have seen this posted a few times on the list here, but it always
> seems to become
On Wed, 2008-05-14 at 19:00 +0400, Ivan Sagalaev wrote:
> Simon Willison wrote:
> > {{ article.something.title }} - outputs text if article is there,
> > fails silently otherwise
> >
> > Which leaves us in a tricky situation. A global settings.py variable
> > for "throw errors on missing template
On Mon, 2008-05-12 at 10:44 -0400, Joshua 'jag' Ginsberg wrote:
> I know it's an obscure and rather inane question, but if one of the
> developers would take a moment to comment, I'd be appreciative.
> Thanks!
>
> -jag
>
> On Thu, May 8, 2008 at 3:33 PM, Joshua 'jag' Ginsberg
> <[EMAIL PROTECTED
On Fri, 2008-04-25 at 17:35 +0200, Wolfram Kriesing wrote:
> thank you for all the quick replies.
> Mmmmh, its good to see that it is there, though I think
> {{ num_files or "no" }}
> looks better and is closer to what I would expect ...
> but thats just an aesthetical thing, I guess.
>
On Fri, 2008-04-18 at 13:28 -0500, James Bennett wrote:
> On Fri, Apr 18, 2008 at 1:21 PM, Jacob Kaplan-Moss
> <[EMAIL PROTECTED]> wrote:
> > That said, I think I agree with Steve's idea of ripping of
> > sys.version_info: we've already stolen so much process from Python why
> > not add to this
As you said, it's a bikeshed argument, so I'm not going to push hard on
this, but I do want to put one thing out for discussion. There is some
value in making versions increase in sort order, so you can do "if
django.VERSION > target:". If 'final' were changed to 'release', this
would work. 'be
On Thu, 2008-04-10 at 20:26 +0200, Gábor Farkas wrote:
> On Thu, Apr 10, 2008 at 06:44:35AM -0700, simonb wrote:
> >
> > On Apr 10, 2:48 pm, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> > > hi,
> > >
> > > would it be a good idea to add support to django to unicode-normalize
> > > incoming get/post-
On Mon, 2008-03-31 at 13:45 -0500, Jacob Kaplan-Moss wrote:
> Right. How will I do this, you say? Here's my plan:
>
> * Using the outline from the existing documentation
> (http://toys.jacobian.org/django/docoutline-r7392/), make a new outline
> and figure out where each bit fits
I made a couple of minor grammatical changes for clarity, but your
english was pretty good, David.
Cheers,
Cliff
On Thu, 2008-02-07 at 15:06 +0100, David Larlet wrote:
>
> Le 6 f�vr. 08 � 21:01, SmileyChris a �crit :
>
> >
> > On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> > wro
24 matches
Mail list logo
