Thanks for the heads up. I'm getting very close to having the test suite 
pass. After I accomplish that goal and establish a more solid reference 
point for django-mssql, I'll look in to the work you've done with adodbapi.

Regards,
Michael Manfre

On Thursday, May 17, 2012 10:14:23 AM UTC-4, VernonCole wrote:
>
> I should mention that if you use pywin32 build 215 or newer, an 
> appropriate version of adodbapi will already be included.  You do not need 
> to download it separately from sourceforge or PyPi unless you are running 
> IronPython. Since pywin32 is already a dependency for django-mssql, you 
> should be covered.  Also, it should not be too hard to add support for 
> ACCESS and 3rd party databases.
> --
> Vernon
>
> On Wednesday, May 16, 2012 2:27:00 PM UTC-6, Michael Manfre wrote:
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/NPgGiBa2iegJ.
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.

Reply via email to