Re: [RFC] Python 3 and MySQL
I run django tests using MySQL-python 1.2.5 (aka, MySQLdb1) and Python 2.7.8. So it means django doesn't work with MySQL with MySQL-python. $ python -V Python 2.7.8 (mysql2)[inada-n@MBA:~] $ pip list MySQL-python (1.2.5) pip (1.5.6) setuptools (3.6) wsgiref (0.1.2) On Tue, Sep 9, 2014 at 5:18 PM, Florian Apolloner wrote: > On Tuesday, September 9, 2014 9:22:10 AM UTC+2, Naoki INADA wrote: >> >> Failed to install index for admin_views.PrePopulatedPostLargeSlug >> model: (1071, 'Specified key was too long; max key length is 767 bytes') > > > Welcome to the wonderful world to mysql, afaik this is a warning and not an > error; so your database driver might convert that incorrectly. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/n-TI8mBcegE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > 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/4bd04867-0f32-4db2-85b3-41671f92aecc%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- INADA Naoki -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CAEfz%2BTxL4E8jYSBrF4jh1H2QTKncQXNAF9uZGJTOshCXf1BxXw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [RFC] Python 3 and MySQL
On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham 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? > > django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: > /var/lib/jenkins/workspace/django-selenium/database/mysql/python/python3.2/tests/.env/lib/python3.2/site-packages/_mysql.cpython-32mu.so: > undefined symbol: PyUnicode_AsUTF8 > > > 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 > > > 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 > > > Let me know if you need tracebacks, but I assume you'll need to run the > tests yourself in our to fix the issues. > > On Monday, September 8, 2014 9:38:22 AM UTC-4, Collin Anderson wrote: >> >> It's great to see us moving forward on this. Thanks to Naoki for all of >> the work on this! > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/n-TI8mBcegE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > 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/fcc06c58-a366-4996-9b57-6412d93c6483%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- INADA Naoki -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CAEfz%2BTyReVRdQFdr_v%2BsS4BXrX1XCAJm2Wj30AO0Qk5fNBOSaw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [RFC] Python 3 and MySQL
> > Naoki, > > Are you aware of performance benchmarks comparing your MySQLdb1 fork and > mysql-connector-python? I'll show you some numbers. But I'm not have time for now. > > About your fork, do you plan to maintain it in the middle/long term? I saw > that issues were not enabled on your Github repo. Is it on purpose? What's > the plan about bug tracking of your fork? > Thanks for pointing it out. I've enabled github issue. I'll maintain mysqlclient-python until MySQLdb1 development is restarted. Since I hope MySQLdb1 and mysqlclient-python merged someday (like setuptools and distribute were merged), I don't want to implement new feature. 'maintain' means bugfix, support new Python, new libmysqlclient and new OS, etc... -- INADA Naoki -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CAEfz%2BTz1DiprvtgeB-ByRcEHZRsLwZF_vOZqoGN-QPY42DMTbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
