Re: Changing deferred model attribute behavior

2013-04-30 Thread Anssi Kääriäinen
On 29 huhti, 00:09, ptone wrote: > A couple just quick observations. > > defer and only are tasks/concepts used when doing a query based on > knowledge of your dataset - adding them to the model itself expands the > number of places where this concept is considered. This has some good and > some b

design decisions for django-mssql: (switching on autocommit and remote proxy) advice wanted.

2013-04-30 Thread VernonCole
Dear knowledgeable persons: I have completed a beta-test version of a Linux remote access server for adodbapi, and have started the process if integrating them into django-mssql. (This is going to be an interesting experience for me -- I have already identified two or three new features that

Re: [GSoC 2013] Revamping validation functionality proposal

2013-04-30 Thread Christopher Medrela
> > On Mon, Apr 29, 2013 at 6:25 AM, Christopher Medrela > wrote: > > Jacob, as you said, I deleted django-updates part, but I ended with a > > proposal taking only 9 weeks. Did you mean also scheduling more than 6 > weeks > > for the first part of the proposal (writing the new framework) an

Re: design decisions for django-mssql: (switching on autocommit and remote proxy) advice wanted.

2013-04-30 Thread Shai Berger
On Tuesday 30 April 2013, VernonCole wrote: > Dear knowledgeable persons: > > I have completed a beta-test version of a Linux remote access server for > adodbapi, and have started the process if integrating them into > django-mssql. (This is going to be an interesting experience for me -- I > ha

Django 1.6 release timeline

2013-04-30 Thread Jacob Kaplan-Moss
Hi folks - Unless there are strong objections, here's what I'm thinking for the Django 1.6 release timeline: Alpha: May 16 Beta: June 20 RC: Aug 1 Final: as early as Aug 8, or later if more RCs are needed. Remember that Alpha is the deadline for "big" features, so if you've got something sizable

Re: Django 1.6 release timeline

2013-04-30 Thread Donald Stufft
On Apr 30, 2013, at 3:31 PM, Jacob Kaplan-Moss wrote: > Hi folks - > > Unless there are strong objections, here's what I'm thinking for the > Django 1.6 release timeline: > > Alpha: May 16 > Beta: June 20 > RC: Aug 1 > Final: as early as Aug 8, or later if more RCs are needed. Sounds reasonabl

Re: Django 1.6 release timeline

2013-04-30 Thread Shai Berger
On Tuesday 30 April 2013, Jacob Kaplan-Moss wrote: > Hi folks - > > Unless there are strong objections, here's what I'm thinking for the > Django 1.6 release timeline: > > Alpha: May 16 > Beta: June 20 > RC: Aug 1 > Final: as early as Aug 8, or later if more RCs are needed. > I see one issue wit

Re: Django 1.6 release timeline

2013-04-30 Thread Andrew Ingram
On 30 Apr 2013, at 23:38, Shai Berger wrote: > I see one issue with this: According to current procedures, if this timeline > is followed, support for 1.4 will be dropped less than 6 months after the > release of 1.5. At least for some of us (which, as I mentioned earlier on the > list, only mo

Re: Django 1.6 release timeline

2013-04-30 Thread Donald Stufft
On Apr 30, 2013, at 7:10 PM, Andrew Ingram wrote: > On 30 Apr 2013, at 23:38, Shai Berger wrote: >> I see one issue with this: According to current procedures, if this timeline >> is followed, support for 1.4 will be dropped less than 6 months after the >> release of 1.5. At least for some of

Re: Django 1.6 release timeline

2013-04-30 Thread Andrew Ingram
On 1 May 2013, at 00:13, Donald Stufft wrote: > > On Apr 30, 2013, at 7:10 PM, Andrew Ingram wrote: > >> On 30 Apr 2013, at 23:38, Shai Berger wrote: >>> I see one issue with this: According to current procedures, if this >>> timeline >>> is followed, support for 1.4 will be dropped less t

Re: Django 1.6 release timeline

2013-04-30 Thread Carl Meyer
On 04/30/2013 05:27 PM, Andrew Ingram wrote: > Absolutely, there's no requirement to migrate, but it does have the > feel of an weird kind of deprecation. Obviously there are > workarounds, like you said, I can upgrade to 1.5 without changing > user models (though that does involve incurring a bit

Re: Django 1.6 release timeline

2013-04-30 Thread Carl Meyer
Hi Shai, On 04/30/2013 04:38 PM, Shai Berger wrote: > On Tuesday 30 April 2013, Jacob Kaplan-Moss wrote: >> Hi folks - >> >> Unless there are strong objections, here's what I'm thinking for the >> Django 1.6 release timeline: >> >> Alpha: May 16 >> Beta: June 20 >> RC: Aug 1 >> Final: as early as

Re: Django 1.6 release timeline

2013-04-30 Thread Andrew Ingram
On 1 May 2013, at 00:35, Carl Meyer wrote: > On 04/30/2013 05:27 PM, Andrew Ingram wrote: >> Absolutely, there's no requirement to migrate, but it does have the >> feel of an weird kind of deprecation. Obviously there are >> workarounds, like you said, I can upgrade to 1.5 without changing >> us

Re: design decisions for django-mssql: (switching on autocommit and remote proxy) advice wanted.

2013-04-30 Thread Russell Keith-Magee
On Tue, Apr 30, 2013 at 9:45 PM, VernonCole wrote: > Dear knowledgeable persons: > > I have completed a beta-test version of a Linux remote access server for > adodbapi, and have started the process if integrating them into > django-mssql. (This is going to be an interesting experience for me -