ticket #14570 for 1.3?

Sorry if I'm being impatient here but I don't want to start raising this question when it's too close to complete feature freeze. Is it possible to include ticket #14570[1] into 1.3 release? It is a rather trivial change which will help generate correct long date display in certain locales. [1] -

Re: Bug with testing framework when not using contrib.auth

On Wed, Nov 3, 2010 at 8:18 AM, David P. Novakovic wrote: > This is certainly an artifact of the fact that messages recent started > supporting anonymous messages. Previously it depended on auth. > > I suspect you just need to open a ticket for this. Yes - this is

Re: Bug with testing framework when not using contrib.auth

This is certainly an artifact of the fact that messages recent started supporting anonymous messages. Previously it depended on auth. I suspect you just need to open a ticket for this. On Wed, Nov 3, 2010 at 4:43 AM, Yo-Yo Ma wrote: > I have a large application that

Bug with testing framework when not using contrib.auth

I have a large application that doesn't user contrib.auth, and when I run `manage.py test` I get a slough of 35 errors, all of which are DatabaseError: no such table: auth_user (differing Tracebacks for each). I don't have any actual tests yet, just the SimpleTest that comes free in tests.py.

Re: Git-using core devs: preference for merge vs. rebase?

On Wed, Nov 3, 2010 at 12:58 AM, Tom X. Tobin wrote: > Do the Git-using core developers have a preference for merge vs. > rebase for updating an upstream-tracking branch?  I prefer to rebase > to keep the changes in question at the branch HEAD, especially if the > branch

Re: Gentle Proposal: add 'render' shortcut in 1.3

On 11/02/2010 05:27 PM, Mikhail Korobov wrote: I'm quite busy now and don't think I'll be able to make the patch ready by 1.3 alpha 1. Full feature freeze is expected only by the time of beta so I don't think it's absolutely necessary to push it before alpha 1. Anyway since I care very much

Re: staticfiles defaults broke my site

On Nov 3, 1:47 am, Carl Karsten wrote: > On Oct 28, 9:45 pm, SmileyChris wrote: > > > My suggestion is that StaticFilesHandler only does its magic if > > 'django.contrib.staticfiles' is found in INSTALLED_APPS. Does that > > sound acceptable? > > Is

Re: Git-using core devs: preference for merge vs. rebase?

On Nov 3, 5:58 am, "Tom X. Tobin" wrote: > Do the Git-using core developers have a preference for merge vs. > rebase for updating an upstream-tracking branch?  I prefer to rebase > to keep the changes in question at the branch HEAD, especially if the > branch hasn't been

Git-using core devs: preference for merge vs. rebase?

Do the Git-using core developers have a preference for merge vs. rebase for updating an upstream-tracking branch? I prefer to rebase to keep the changes in question at the branch HEAD, especially if the branch hasn't been pushed publicly yet, but a rebase for something that *has* been pushed

Re: Gentle Proposal: add 'render' shortcut in 1.3

I'm quite busy now and don't think I'll be able to make the patch ready by 1.3 alpha 1. On 2 ноя, 20:06, Mikhail Korobov wrote: > Hi all. > > The new patch is attached to ticket > (seehttp://code.djangoproject.com/attachment/ticket/12816/render_shortcut... > ). Docs are

Re: Gentle Proposal: add 'render' shortcut in 1.3

Hi all. The new patch is attached to ticket (see http://code.djangoproject.com/attachment/ticket/12816/render_shortcut.6.diff?format=raw ). Docs are cumbersome (and incomplete), and a couple of middleware tests are missing. 1) Template response middleware is introduced. It is applied only for

Re: staticfiles defaults broke my site

On Oct 28, 9:45 pm, SmileyChris wrote: > My suggestion is that StaticFilesHandler only does its magic if > 'django.contrib.staticfiles' is found in INSTALLED_APPS. Does that > sound acceptable? Is it really an app? If not, I suggest STATICFILES_URL defaults to None, and

Re: Django/CherryPy problem with POST data

On Tue, Nov 2, 2010 at 4:19 AM, Ivan Sagalaev wrote: > On 11/01/2010 11:21 AM, Mark wrote: >> >> Ticket #14594 >> > > From a quick look it can be fixed in two ways: > > - HttpRequest.raw_post_data can always explicitly ask