+1 to removing the psycopg1 backend. I was just wondering if it was ever going to happen earlier today when I was creating example settings files for running the tests, and got tired of typing 'postgresql_psycopg2'. Even getting psycopg1 installed is a small PITA on any modern Linux system. I'll hold my breath in anticipation of your renaming plan, too.
On Sat, Dec 12, 2009 at 8:09 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Django 1.2 ships. Users read the release notes, and notice that > psycopg1 is now deprecated and will be removed. It's still there, and > still supported, so they can upgrade quickly and not have to be stuck > on 1.1. Plus, those who care about these things can enable the PendingDeprecationWarnings if they want to. It certainly doesn't hurt and it probably helps a few folks. It's how everything else is deprecated and it makes sense. I see no reason to change the plan. Tobias -- Tobias McNulty Caktus Consulting Group, LLC P.O. Box 1454 Carrboro, NC 27510 (919) 951-0052 http://www.caktusgroup.com -- 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 this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
