Home > Uncategorized > Moving Django backend out of MySQL Connector/Python’s trunk

Moving Django backend out of MySQL Connector/Python’s trunk

October 2nd, 2009 Leave a comment Go to comments

Today I removed the Django backend using MySQL Connector/Python out of the trunk and made it available through another branch on Launchpad. I’m not officially maintaining this, but it is used in my Django-powered homepage. I had to pull it out because I couldn’t keep up compatibility with newer versions.
Maybe a backend using Connector/Python 1.0 might go into Django as an alternative to MySQLdb? Who knows!

Share
Tags: ,
  1. Marco
    October 2nd, 2009 at 13:18 | #1
    Reply | Quote

    django had a mysql backend that didn't force us to compile MySQLdb ?
    where it's documented ?

  2. Geert JM Vanderkelen
    October 4th, 2009 at 09:41 | #2
    Reply | Quote

    @Marco

    I made my own Django DB back-end using MySQL Connector/Python. It was part of the Connector/Python source tree.

    So it was never part of official Django distribution. Sorry if I have caused confusion there.

  3. Marco
    October 4th, 2009 at 16:07 | #3
    Reply | Quote

    2 questions:

    about this MySQL Connector/Python shouldn't it be transparent from the django point of view ? I mean if I use MySQL Connector/Python or MySQLdb django should not notice the difference right ?

    2nd: is this Connector able to run on jython ?

    cheers

  1. No trackbacks yet.