A few weeks ago, I started down the path of updating django-mssql so that it supports Django 1.4. I moved the project over to bitbucket ( http://bitbucket.org/Manfre/django-mssql/), docs are deployed to read the docs (http://django-mssql.readthedocs.org), and have made it a policy of deploying packages to PyPi.
Django 1.4 support is mostly there and so far is passing all testing for the site responsible for the backend's existence (http://www.src.org). To help avoid surprises and ensure life as a 3rd party database backend maintainer is a lot less painful, I have set a goal of having django-mssql pass the test suite. This is a non-trivial task that will require changes to django and django-mssql. I've already submitted a few tickets that bring me closer to my goal and it was advised that I send this message as a heads up regarding my intentions to avoid tickets being closed with a "mssql isn't officially supported by Django" comment. If you review one of these tickets, please keep my goal in the back of your mind. I welcome feedback on better ways of approaching my proposed changes. Regards, Michael Manfre -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
