Re: [RFC] Python 3 and MySQL

I started the ball rolling on getting mysqlclient packaged in Debian/Ubuntu. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768096 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from

Re: [RFC] Python 3 and MySQL

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

Re: [RFC] Python 3 and MySQL

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

Re: [RFC] Python 3 and MySQL

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

Re: [RFC] Python 3 and MySQL

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: >

Re: [RFC] Python 3 and MySQL

Python 2.7.3 and MySQL_python-1.2.5-cp27-none-linux_x86_64.whl On Tuesday, September 9, 2014 10:41:40 AM UTC+2, Naoki INADA wrote: > > 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

Re: [RFC] Python 3 and MySQL

http://djangoci.com/ disagrees with you :) Would have to check the specific mysqldb version. -- 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

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

Re: [RFC] Python 3 and MySQL

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

Re: [RFC] Python 3 and MySQL

I can't run django test. Synchronizing apps without migrations: Creating tables... Installing custom SQL... Installing indexes... Failed to install index for admin_views.PrePopulatedPostLargeSlug model: (1071, 'Specified key was too long; max key length is 767 bytes') I use 1.7 tag on

Re: [RFC] Python 3 and MySQL

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,

Re: [RFC] Python 3 and MySQL

I also don't need python 3.2 support (or even python 3.3 support for that matter) -- 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

Re: [RFC] Python 3 and MySQL

I don't think it'd be a problem, but I don't use MySQL or Python 3.2 on a regular basis. On Monday, September 8, 2014 11:19:56 AM UTC-4, Naoki INADA wrote: > > On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham > wrote: > > We'd need mysqlclient to support Python 3.2 (or drop

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

Re: [RFC] Python 3 and MySQL

We'd need mysqlclient to support Python 3.2 (or drop official support for MySQL/Python 3.2): django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module:

Re: [RFC] Python 3 and MySQL

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 the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [RFC] Python 3 and MySQL

I'll test mysqlclient-python on my staging CI server today. On Monday, September 8, 2014 3:08:41 AM UTC-4, Claude Paroz wrote: > > Le lundi 8 septembre 2014 08:33:39 UTC+2, Naoki INADA a écrit : >> >> >> On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: >>> >>> > >>> > Naoki,

Re: [RFC] Python 3 and MySQL

Ohh wow. I also just noticed CyMySQL, which is a fork of PyMySQL with optional C speedups. It seems like a good idea in theory, though it appears to have diverged from PyMySQL a bit. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: [RFC] Python 3 and MySQL

Le lundi 8 septembre 2014 08:33:39 UTC+2, Naoki INADA a écrit : > > > On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: >> >> > >> > Naoki, >> > >> > Are you aware of performance benchmarks comparing your MySQLdb1 fork >> and >> > mysql-connector-python? >> > > I've posted

Re: [RFC] Python 3 and MySQL

On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: > > > > > 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. > I've posted quick benchmark:

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

Re: [RFC] Python 3 and MySQL

I'm warming up to mysqlclient. I assume it has better performance or is more correct than pymysql? Is there any hope to getting the package included in debian/ubuntu? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from

Re: [RFC] Python 3 and MySQL

Claude, it looks like Naoki opened up Issues on the repository. Coincidentally, I just opened a Django Ticket related to this: https://code.djangoproject.com/ticket/23446 I had not seen this thread until Tim Graham pointed it out. See that ticket for my views on the matter. tldr: recommending

Re: [RFC] Python 3 and MySQL

On Thursday, August 14, 2014 3:01:07 PM UTC+2, Naoki INADA wrote: > > > MySQL-Connector/Python was not so popular (as far as I know). > But 1.2.2 GA was released recently. It looks nice to me. It may be > popular if Django recommend it. > It's repository was moved from launchpad to github. >

Re: [RFC] Python 3 and MySQL

On Wednesday, August 13, 2014 1:41:22 AM UTC+9, Tim Graham wrote: > > I'd like see some community consensus on the best solution for a MySQL > adapter rather than than have more than one build for MySQL. > > I don't know the MySQL ecosystem very well. Naoki, is there no interest > from MySQLdb

Re: [RFC] Python 3 and MySQL

I'd like see some community consensus on the best solution for a MySQL adapter rather than than have more than one build for MySQL. I don't know the MySQL ecosystem very well. Naoki, is there no interest from MySQLdb in your Python 3 compatibility changes? On the PyPI page it says, "Python-3.0

Re: [RFC] Python 3 and MySQL

While we're on the topic, I'd like to propose (also?) supporting the pure-python, MySQLdb-compatible pymysql, which INADA Naoki (methane) has also put a lot of work into. pymysql is pure-python, so it's really easy to get up-and running on Mac OS X and in other environments, because you don't

[RFC] Python 3 and MySQL

Hi, folks. I believe most popular MySQL driver for Python is MySQL-python (MySQLdb). http://py3readiness.org/ shows MySQL-python is the 4th popular package that does not support Python 3. I've forked MySQL-python because I want to move Python 3 completely ASAP.