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/3f29471a-c174-4985-8018-881f866edaa0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to