Re: Proposal: ModelForm API improvements

2013-03-08 Thread Aaron Merriam
+1 This would be great. On Thursday, March 7, 2013 12:42:29 PM UTC-7, Bruno ReniƩ wrote: > > Hello, > > There was some discussion on the current limitations of the ModelForm > API in the past couple of days on IRC, I'd like to make a proposal to > address some of them. > > I wrote django-flop

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread Thejaswi Puthraya
On Thursday, March 7, 2013 10:18:11 PM UTC+5:30, Jacob Kaplan-Moss wrote: > > Hi folks -- > > This one's simple: I'd like to deprecate `django.contrib.comments`, > scheduling it to be removed in a couple of releases. [snipped] > Any objections? > As the student (back then) who worked on

Re: Django sanctioned extensions

2013-03-08 Thread Russell Keith-Magee
On Fri, Mar 8, 2013 at 11:23 AM, wrote: > from thread "Moving database backends out of the core" > > On Mar 7, 2013, at 5:13 PM, Russell Keith-Magee > wrote: > > > There is, however, a possible middle ground, following the example set > by Flask: we introduce to Django a list of "officially reco

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread Adrian Holovaty
On Fri, Mar 8, 2013 at 12:38 AM, Jacob Kaplan-Moss wrote: > On Thu, Mar 7, 2013 at 5:55 PM, Russell Keith-Magee > wrote: >> However, I'd argue against using /dev/null as a disposal mechanism. I don't >> think the code should ever completely disappear. If someone offers to take >> over, that's gre

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread Val Neekman
Yep. +1 Val Sent from my mobile device. On 2013-03-07, at 11:48 AM, Jacob Kaplan-Moss wrote: > Hi folks -- > > This one's simple: I'd like to deprecate `django.contrib.comments`, > scheduling it to be removed in a couple of releases. > > My rationale is this: if you don't really care much a

Re: Request for review: database-level autocommit

2013-03-08 Thread Florian Apolloner
Hi Aymeric, On Friday, March 8, 2013 11:32:52 PM UTC+1, Aymeric Augustin wrote: > > Carl was kind enough to review the branch in detail. (Thank you!) > > I'll take his feedback into account, clean up the history, and push a new > version tomorrow. I hope to merge it during the week-end. > If you

Re: Moving database backends out of the core

2013-03-08 Thread Florian Apolloner
On Friday, March 8, 2013 3:35:53 PM UTC+1, Michael Manfre wrote: > > If we have MSSQL in core I'd really like to be able to talk with it from a > Linux machine too, it would also make testing easier since we'd just need a > VBox with MSSQL ;) Supporting a commercially available product but > req

Re: Request for review: database-level autocommit

2013-03-08 Thread Aymeric Augustin
On 7 mars 2013, at 17:37, Aymeric Augustin wrote: > Barring unexpected problems and last minute vetoes, I plan to merge > this branch when another core dev reviews it thoroughly and accepts it, Carl was kind enough to review the branch in detail. (Thank you!) I'll take his feedback into accou

Re: Moving database backends out of the core

2013-03-08 Thread Michael Manfre
On Fri, Mar 8, 2013 at 9:33 AM, Javier Guerra Giraldez wrote: > On Fri, Mar 8, 2013 at 4:25 AM, VernonCole wrote: > > People tend to think of ADO as only talking to Microsoft databases. > Nothing > > could be farther from the truth. When maintaining adodbapi, I normally > test > > against MS-SQ

Re: Moving database backends out of the core

2013-03-08 Thread Michael Manfre
On Fri, Mar 8, 2013 at 6:35 AM, Florian Apolloner wrote: > What's the state of http://code.google.com/p/pymssql/ ? > Their stable release relies upon a no longer supported Microsoft driver and has some known issues that make it unusable (lack of MARS support being the biggest issue encountered in

Re: Moving database backends out of the core

2013-03-08 Thread Javier Guerra Giraldez
On Fri, Mar 8, 2013 at 4:25 AM, VernonCole wrote: > People tend to think of ADO as only talking to Microsoft databases. Nothing > could be farther from the truth. When maintaining adodbapi, I normally test > against MS-SQL Server, Microsoft "Jet" (a.k.a. ACCESS), MySQL, and postgres. > I have al

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread Thiago Avelino
+1 Cheers, Thiago Avelino On Fri, Mar 8, 2013 at 10:19 AM, Richard Bronosky wrote: > Yes. Aymeric, you covered every point I wanted to make. > > Sent from my Samsung Galaxy S3 using the Swype software keyboard. > --Richard Bronosky > On Mar 7, 2013 12:00 PM, "Aymeric Augustin" < > aymeric.au

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread Richard Bronosky
Django should have a boneyard. Here is the homebrew boneyard https://github.com/Homebrew/homebrew-boneyard Sent from my Samsung Galaxy S3 using the Swype software keyboard. --Richard Bronosky On Mar 7, 2013 7:39 PM, "Jacob Kaplan-Moss" wrote: > On Thu, Mar 7, 2013 at 5:55 PM, Russell Keith-Magee

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread Richard Bronosky
Yes. Aymeric, you covered every point I wanted to make. Sent from my Samsung Galaxy S3 using the Swype software keyboard. --Richard Bronosky On Mar 7, 2013 12:00 PM, "Aymeric Augustin" < aymeric.augus...@polytechnique.org> wrote: > On 7 mars 2013, at 17:48, Jacob Kaplan-Moss wrote: > > > This on

Django sanctioned extensions

2013-03-08 Thread ryan
from thread "Moving database backends out of the core" On Mar 7, 2013, at 5:13 PM, Russell Keith-Magee wrote: > There is, however, a possible middle ground, following the example set by > Flask: we introduce to Django a list of "officially recognised" extensions. > These extensions are still m

Re: Moving database backends out of the core

2013-03-08 Thread Florian Apolloner
Hi, On Friday, March 8, 2013 4:24:00 AM UTC+1, Michael Manfre wrote: > > django-mssql is actively maintained and will be for at least the next few > years because it's used for my employer's production site that is critical > to business operations. The backend also supports stored procedures al

Re: Moving database backends out of the core

2013-03-08 Thread VernonCole
I would love to volunteer for the project of MSSQL support. It happens that django-mssql uses a fork of my adodbapi v2.1 code. I pulled those changes back into the main branch of adodbapi (and did a lot of useful refactoring thanks to the good work done on the fork) at version 2.3. Apparently

Re: Proposal: deprecate and remove django.contrib.comments

2013-03-08 Thread shacker
Sorry, but -1 from me. Given the core premise that the job of a web application framework is to find the common features that many websites need to implement and make them easy to achieve, commenting definitely fits into this category. I run two sites that use Django comments heavily. Django c