exception handling memory leak...

http://code.djangoproject.com/ticket/10758 Can we fix this? It's a pretty easy fix. thanks, -k -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from

[GSOC] Query-Refactor

Hey all, As you're likely aware this summer I'll be a GSOC student responsible for query-refactor (aka "NoSQL") in Django. Basically the next couple of weeks are going to involve me ripping up a bunch of internals, and in the interest of keeping the SVN branch stable I'll be committing that work

Re: Proposal: Replace django.contrib.formtools.wizard

On Sat, May 29, 2010 at 22:07, Stephan Jäkel wrote: > I already discussed this ticket with Jannis during the sprints and hope to > start a discussion here to find the right way to allow file uploads and see > if my approach takes the right direction. > Couldn't you just use

Re: Proposal: Replace django.contrib.formtools.wizard

On Sun, May 30, 2010 at 12:33 PM, Harro wrote: > We had a site where we needed a wizard with the ability to go back and > forward and store files. > Only allowing files in the last step really isn't an option imho, that > just avoiding the problem ;-) > > What we did was

Re: More flexible choices validation in models.Field

On 29.05.2010 19:23, Jannon Frank wrote: This produces a validation error on MyModel because it is checking the combined string (e.g. '1,2,5') against the list of choices, when the intent is to have each of the values in the string checked individually against the choices. Is there any

Re: Proposal: Replace django.contrib.formtools.wizard

We had a site where we needed a wizard with the ability to go back and forward and store files. Only allowing files in the last step really isn't an option imho, that just avoiding the problem ;-) What we did was simply store the files in a temporary folder and have a management command to clean

Re: Proposal: Replace django.contrib.formtools.wizard

Hey Steph -- I've had a chance to play with your code, and I'm impressed and generally +1 on replacing formwizard with yours. I couldn't tell from my quick play, though, if there were any backwards-incompatible changes. There's a fair bit of code churn (in a good way :), so before we could merge

Re: Class based generic views in 1.3?

Maybe I missed something, but why don't you use __new__ instead of copying the instance? Bye, Waldemar On May 29, 11:06 pm, Ben Firshman wrote: > Luke, you're absolutely right that changing the definition of a view is a bad > idea, it just seemed the best solution then. >

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

-1. The only issue that I have with sites is that the default site should be 127.0.0.1:8000 since that's what runserver defaults to. Putting example.com as SITE_ID 1 only makes novice django developers shout and throw things because like me they 'add 127.0.0.1:8000 and delete example.com' instead