Test failures are fixed with mysqlclient 1.3.3. I believe we can now move the discussion of the implementation of this to the ticket: https://code.djangoproject.com/ticket/23446
There are some tickets about pymysql (below), but I have some reservations about officially supporting more than one MySQL connector since our buildbot would presumably need to test all of them. https://code.djangoproject.com/ticket/20542 https://code.djangoproject.com/ticket/22391 On Tuesday, September 9, 2014 3:32:47 PM UTC-4, Corey Farwell wrote: > > It is a valid concern. That said, I'd rather the documentation recommend a > GPL, Python 3+2, working MySQL connector over a GPL, Python 2, partially > broken MySQL connector. > > On Tuesday, September 9, 2014 3:21:08 PM UTC-4, Daniel Sears wrote: >> >> Aside from the technical issues, there are the licensing issues. The >> Django community strongly prefers BSD-style licensing and both mysqldb and >> MySQL Connector/Python use GPL licenses. For an e-mail thread which >> addresses these GPL issues, see >> >> >> https://groups.google.com/forum/#!msg/django-developers/8r_RVmUe5ys/09lCwJl-L1kJ >> >> PyMySQL does appear to have a BSD-like license. >> >> --Dan >> >> >> On Tuesday, September 9, 2014 8:26:37 AM UTC-7, Naoki INADA wrote: >>> >>> I've fixed them and released mysqlclient 1.3.3. >>> https://pypi.python.org/pypi/mysqlclient >>> >>> On Tuesday, September 9, 2014 3:29:45 PM UTC+9, Naoki INADA wrote: >>>> >>>> I've fixed `%(xxx)s` style formatting. >>>> >>>> I have not changed error switch: >>>> https://github.com/PyMySQL/mysqlclient-python/blob/master/_mysql.c#L150 >>>> https://github.com/farcepest/MySQLdb1/blob/master/_mysql.c#L180 >>>> >>>> I'll investigate the problem, but I can't promise any date for fixing >>>> it. >>>> >>>> >>>> On Tuesday, September 9, 2014 12:35:26 AM UTC+9, Claude Paroz wrote: >>>>> >>>>> On Monday, September 8, 2014 5:19:56 PM UTC+2, Naoki INADA wrote: >>>>>> >>>>>> On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham <[email protected]> >>>>>> wrote: >>>>>> > We'd need mysqlclient to support Python 3.2 (or drop official >>>>>> support for >>>>>> > MySQL/Python 3.2): >>>>>> >>>>>> Python 3.3 introduces PEP 393 (Flexible String Representation) and >>>>>> many Unicode API has >>>>>> been changed and deprecated. It also introduce unicode literal. >>>>>> Supporting Python 3.2 will make code messy. >>>>>> >>>>>> I want to drop Python 3.2 support since I believe most Python 3 users >>>>>> are aggressive enough >>>>>> to go forward. >>>>>> >>>>>> How Python 3.2 important for you? >>>>>> >>>>> >>>>> I think we could live with MySQL not supporting Python 3.2. >>>>> >>>>> > Python 2.7 test failures: >>>>>> > >>>>>> > >>>>>> > custom_pk.tests.CustomPKTests.test_required_pk >>>>>> > fixtures.tests.FixtureLoadingTests.test_loaddata_error_message >>>>>> > >>>>>> generic_relations_regress.tests.GenericRelationTests.test_target_model_is_unsaved >>>>>> >>>>>> >>>>>> > >>>>>> get_or_create.tests.GetOrCreateTests.test_get_or_create_invalid_params >>>>>> > get_or_create.tests.UpdateOrCreateTests.test_integrity >>>>>> > model_fields.tests.BooleanFieldTests.test_null_default >>>>>> >>>>> >>>>> Thanks Tim for testing. These errors seem to all have the same origin, >>>>> null inserts into not-null columns generate OperationalError instead of >>>>> IntegrityError. >>>>> >>>>> >>>>>> > Python 3.4 test failures: >>>>>> > >>>>>> > >>>>>> > backends.tests.BackendTestCase.test_cursor_execute_with_pyformat >>>>>> > >>>>>> backends.tests.BackendTestCase.test_cursor_executemany_with_pyformat >>>>>> > >>>>>> backends.tests.BackendTestCase.test_cursor_executemany_with_pyformat_iterator >>>>>> >>>>>> >>>>>> > custom_pk.tests.CustomPKTests.test_required_pk >>>>>> > fixtures.tests.FixtureLoadingTests.test_loaddata_error_message >>>>>> > >>>>>> generic_relations_regress.tests.GenericRelationTests.test_target_model_is_unsaved >>>>>> >>>>>> >>>>>> > >>>>>> get_or_create.tests.GetOrCreateTests.test_get_or_create_invalid_params >>>>>> > get_or_create.tests.UpdateOrCreateTests.test_integrity >>>>>> > model_fields.tests.BooleanFieldTests.test_null_default >>>>>> > raw_query.tests.RawQueryTests.test_pyformat_params >>>>>> >>>>>> >>>>> In addition of the above issue, it seems that pyformat isn't supported >>>>> for Python3. Something around these lines: >>>>> cursor.execute("INSERT INTO table f1, f2 values(%(val1)s, %(val2)s)", >>>>> {"val1": value_1, "val2": value_2}) >>>>> >>>>> I've created issues on the mysqlclient bug tracker. >>>>> https://github.com/PyMySQL/mysqlclient-python/issues/3 >>>>> https://github.com/PyMySQL/mysqlclient-python/issues/4 >>>>> >>>>> Claude >>>>> >>>>> >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/147e8e42-7189-46f9-83e8-f2f81b0dbb4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
