Decision needed on formfield_callback

I'm wondering if we can open a quick discussion on the `formfield_callback` method of django ModelForms.. The basic issue boils down to the fact that we have an undocumented (and thus unsupported) method on ModelForm that would benefit greatly from a small change in behavior and an official

Re: How can we Commit request.FILES using pysvn in Django?

This is a group for discussing development of the framework. Please post your support questions to django-users. On Tuesday, February 26, 2013 7:57:24 AM UTC+1, abdul wrote: > > I have to commit files from request.FILES to svn repository usiong pysvn > but when i try like this > > import pysvn

DjangoCon Europe tickets on sale today!

Hi everyone! I'm Ola, one of the main organizers of upcoming DjangoCon Europe conference. I just wanted to let you know that we're starting to sell regular tickets to the conference today at 4pm CET prompt! Tickets are available here: http://tickets.djangocon.eu/ We have also recently

Re: [SPAM] Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi Shai, On Tuesday, February 26, 2013 2:18:14 AM UTC+1, Shai Berger wrote: > > > No, since the Oracle tests are somewhat slow we decided to just test one > > Python for now. I will try to see if Python 2 makes a difference, didn't > > yet think of it. > > > > Cool. > They do work on

Re: DjangoCon Europe tickets on sale today!

I just wanted to say that the list of talks & speakers is the best I've seen to date. I really wish I could go see it, but unfortunately Warsaw is too far for me. I wonder if these will ever be made available online for a fee, even if months after the conference. For a hobbyist developer like me,

Re: deprecation of AUTH_PROFILE_MODULE

I looked into this today with 1.5 hitting and working on a project and this seemed relevant. On Monday, 2 May 2011 19:22:53 UTC+2, Carl Meyer wrote: > 1. A specification of the minimal useful interface for a User (perhaps > > in the form of an abstract base model?) > A User should not require

Moving from PIL to Pillow

Hi all, Why isn't Pillow the recommended Django image library yet? PIL has been unmaintained for almost 3 years and has a number of annoying bugs (e.g. fails to open some valid JPEG files, maybe has some security issues as well). Pillow, on the other hand, is a backwards-compatible

Re: DjangoCon Europe tickets on sale today!

On 27-02-13 21:21, Andre Terra wrote: I wonder if these will ever be made available online for a fee, even if months after the conference. For a hobbyist developer like me, coughing up a few thousand dollars for the tickets, registration and hotel is just impossible, but I would be glad to pay

Re: Decision needed on formfield_callback

On Wednesday 27 February 2013, poswald wrote: > I'm wondering if we can open a quick discussion on the `formfield_callback` > method of django ModelForms.. > > The basic issue boils down to the fact that we have an undocumented (and > thus unsupported) method on ModelForm that would benefit

Re: Moving from PIL to Pillow

On 27 févr. 2013, at 21:40, Marijonas Petrauskas wrote: > Why isn't Pillow the recommended Django image library yet? PIL has > been unmaintained for almost 3 years and has a number of annoying bugs > (e.g. fails to open some valid JPEG files, maybe has some security > issues

Re: deprecation of AUTH_PROFILE_MODULE

On Thu, Feb 28, 2013 at 4:24 AM, Alper Çuğun wrote: > > I looked into this today with 1.5 hitting and working on a project and > this seemed relevant. > > On Monday, 2 May 2011 19:22:53 UTC+2, Carl Meyer wrote: > >> 1. A specification of the minimal useful interface for a User

Re: Moving from PIL to Pillow

On Wed, Feb 27, 2013 at 4:42 PM, Aymeric Augustin wrote: > > On 27 févr. 2013, at 21:40, Marijonas Petrauskas wrote: > > > Why isn't Pillow the recommended Django image library yet? PIL has > > been unmaintained for almost 3 years and has a

first() and last(), earliest() and latest()

Hi all, We struggled to get a proper definition for a first() and last() method vs. earliest() and latest() . I'd like to make one proposal. After that, I really like your opinion on which syntax you prefer. First, let me give you a lenghty introduction. We discussed several use cases on this

Re: [SPAM] Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi Florian, On Wednesday 27 February 2013, Florian Apolloner wrote: > Hi Shai, > > On Tuesday, February 26, 2013 2:18:14 AM UTC+1, Shai Berger wrote: > > > No, since the Oracle tests are somewhat slow we decided to just test > > > one Python for now. I will try to see if Python 2 makes a

Re: first() and last(), earliest() and latest()

On 27 févr. 2013, at 23:34, Wim Feijen wrote: > Therefore, my proposal is, if we are going to implement the earliest and > latest method, we should definitely rename them to: first and latest. I believe that latest() was introduced with dates in mind, and then earliest()

Persistent connections, take 2

Hello, I've integrated the feedback received on my initial proposal in a new pull request: https://github.com/django/django/pull/733 and I think it's ready for review. I'm just wondering if 10 minutes is a good default value for CONN_MAX_AGE. I chose it randomly. Would "unlimited" be better?

Re: first() and last(), earliest() and latest()

On Thursday 28 February 2013, Aymeric Augustin wrote: > > I would support renaming them to first / last through a deprecation path. > The new aliases would be available immediately, the old ones would be > removed in two versions. > +1 > And while we're there, I suggest to rely on the existing

Re: first() and last(), earliest() and latest()

Oopsie: On Thursday 28 February 2013, Shai Berger wrote: > > Note that with this suggestion: > > qset.filter(a=b).first(c) > > is not equivalent to > > qset.order_by(c).filter(a=b) > That should have read qset.order_by(c).first(a=b) Shai. -- You received this message

Re: first() and last(), earliest() and latest()

On 02/27/2013 05:34 PM, Wim Feijen wrote: Hi all, We struggled to get a proper definition for a first() and last() method vs. earliest() and latest() . I'd like to make one proposal. After that, I really like your opinion on which syntax you prefer. First, let me give you a lenghty