Re: Allow bypassing validation in newforms (#5153)

On Mon, 2007-09-17 at 00:23 +0200, Christopher Lenz wrote: > Hey all, > > I've created a ticket which has been closed as wontfix, and was told > to bring it here. So here I am. > > I'm somewhere between -0 and -1 on this, for a couple of reasons.

Re: Django is slower after changeset [6333]

OK, after all, the main change it's already commited, and is the important one. On 17 sep, 01:24, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-09-16 at 11:21 -0700, msaelices wrote: > > I created a ticket for it. Ticket is: > >http://code.djangoproject.com/ticket/5513 > > > After

Re: Django is slower after changeset [6333]

On Sun, 2007-09-16 at 11:21 -0700, msaelices wrote: > I created a ticket for it. Ticket is: > http://code.djangoproject.com/ticket/5513 > > After more than one hour of profiling, I found the problem. It creates > a session for every request. > > I've attached patch on ticket: > http://code.djang

Re: Heads-up: doing a bit of triage work

On Sun, 2007-09-16 at 15:34 -0500, James Bennett wrote: > On 9/16/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > s/would/will/ -- I'm gonna try to have this wrapped up in the next couple > > days. > > Cool. I've paused for a bit of a break, but here's some info on what > I've been doing. >

Re: Allow bypassing validation in newforms (#5153)

On Mon, 2007-09-17 at 00:23 +0200, Christopher Lenz wrote: > So yeah, I want to be able to show previews of data that may at that > point not be valid. Imagine there's a form with 12 required fields, > and I want to enable users to see what their entry would look like > even before they've c

Ticket #5516--Allow apps to provide their own commands to django-admin.py

http://code.djangoproject.com/ticket/5516 I just uploaded a patch that seems to allow apps to register their own commands for django-admin.py. However, smarter people than I have tried the same thing previously, so I'd appreciate it if some of those people would take a look and try to break it.

Re: Allow bypassing validation in newforms (#5153)

On 9/16/07, Christopher Lenz <[EMAIL PROTECTED]> wrote: > contrib.formtools.FormPreview implements a different kind of > approach, and can't be used for this. I would personally think that, if there's a need for this, the solution would be to extend or subclass FormPreview somehow to enable it, b

Allow bypassing validation in newforms (#5153)

Hey all, I've created a ticket which has been closed as wontfix, and was told to bring it here. So here I am. So yeah, I want to be able to show previews of data that may at that point not be valid. Imagine there's a form with 12 required field

Re: Heads-up: doing a bit of triage work

And now that I've marked #5515 accepted, I'm done. Couple more "master tickets": * Pagination template tags: #3169 * SQLite "off by one" date filtering errors: #3689 * Generic views unit tests: #5506 The mighty effbot informs me that, since the sprint started: 237 commits 413 tickets closed 11

Re: Heads-up: doing a bit of triage work

On 9/16/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > s/would/will/ -- I'm gonna try to have this wrapped up in the next couple > days. Cool. I've paused for a bit of a break, but here's some info on what I've been doing. My process today has been to simply go to the big list of open ticke

Re: Heads-up: doing a bit of triage work

And a nice number to think about with respect to this sprint: When I started this morning, effbot's timeline scraper showed 278 tickets closed since the start of the sprint. As of the last update seven minutes ago, it shows 402 tickets closed. We should do this more often :) -- "Bureaucrat Con

Re: Heads-up: doing a bit of triage work

On 9/16/07, James Bennett <[EMAIL PROTECTED]> wrote: > * Lots of things related to FileField which would be fixed by the > pluggable backends proposal. s/would/will/ -- I'm gonna try to have this wrapped up in the next couple days. Jacob --~--~-~--~~~---~--~~ You

#689: using REMOTE_USER

I added a new patch to ticket 689. This one does not use settings (thanks Joseph Kocherhans). It combines the use of a middleware and an authentication backend to use the Remote_user information passed down by apache. This is usefull in intranets where you can use apache with mod_ntlm or mod_auth_

Re: Django is slower after changeset [6333]

On 16 sep, 20:58, msaelices <[EMAIL PROTECTED]> wrote: > This is the last patch update: > > http://code.djangoproject.com/attachment/ticket/5513/sessions_speedup... Sorry, the correct link is this: http://code.djangoproject.com/attachment/ticket/5513/sessions_speedup_6364.2.diff > > It improv

Re: Django is slower after changeset [6333]

This is the last patch update: http://code.djangoproject.com/attachment/ticket/5513/sessions_speedup_6364.2.diff It improve performance a little, but It's difficult to test because differences are minimal. On 16 sep, 20:21, msaelices <[EMAIL PROTECTED]> wrote: > I created a ticket for it. Ticke

Django is slower after changeset [6333]

I created a ticket for it. Ticket is: http://code.djangoproject.com/ticket/5513 After more than one hour of profiling, I found the problem. It creates a session for every request. I've attached patch on ticket: http://code.djangoproject.com/attachment/ticket/5513/sessions_speedup_6364.diff Agai

Re: Etiquette for doc typo

On 9/16/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > I noticed a small problem in a change to some admin docs for a patch I > submitted that was accepted. Should I reopen the closed ticket and > attach the patch to it or should I create a new ticket and reference the > first one? Re-open with a

Etiquette for doc typo

I noticed a small problem in a change to some admin docs for a patch I submitted that was accepted. Should I reopen the closed ticket and attach the patch to it or should I create a new ticket and reference the first one? Todd --~--~-~--~~~---~--~~ You received t

Re: Call to Arms -- Caching Mechanisms

Anybody has testing the performance of new improvements in session storage? In changeset http://code.djangoproject.com/changeset/6333 was implementing session backends for filesystem and memcached. This might improve performance of a site, freeing database for hard work. On 15 sep, 03:22, David C

Heads-up: doing a bit of triage work

While scanning the open tickets list I noticed there are lot of tickets which fall into the following categories: * Requests for very specific admin customizations which will be obsoleted by newforms-admin, or which are already possible with the limited customization offered by the current admin.

The best Site of the World

http://www.rettet-den-affen.de.tl/ --~--~-~--~~~---~--~~ 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, s

Re: Migrating to new-admin...

jdetaeye wrote: > Personally, I feel the page is still very much "developer-oriented", > rather than "django-user-oriented". E.g. the refs to ticket numbers are > useful for the developer, but not for somebody who wants to get going > with the new-admin. > Given a green light I am willing to edi

Re: BooleanField and NullBooleanField (#2855 again)

Reading http://code.djangoproject.com/ticket/3997, I think this covers the BooleanField side of thinsg On Aug 1, 2:12 pm, SmileyChris <[EMAIL PROTECTED]> wrote: > /me pulls out his horse-beating stick... > > First off, the patch in the ticket [1] this thread mentions isn't the > correct solution.

Re: Migrating to new-admin...

Joseph, I edited the page according to the above. Personally, I feel the page is still very much "developer-oriented", rather than "django-user-oriented". E.g. the refs to ticket numbers are useful for the developer, but not for somebody who wants to get going with the new-admin. Given a green