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. > https://github.com/oracle/mysql-connector-python > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Foracle%2Fmysql-connector-python&sa=D&sntz=1&usg=AFQjCNFNOI5cRNeieEYsHvTIfn_aL5w22w> > > Although it looks nice to me, there are 2 drawbacks. > > * They don't put package to PyPI. `--allow-external > mysql-connector-python` option is required for `pip install`. > * Although repository was moved to Github, bug database is still bit > unfriendly (http://bugs.mysql.com/ ). > > > I think if Oracle will be more familiar with OSS community (accepting pull > requests, using Travis-CI, etc...), > It can replace PyMySQL. Because it's development is more active than us. >
Naoki, Are you aware of performance benchmarks comparing your MySQLdb1 fork and mysql-connector-python? 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? 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/ca6afdc5-a5f2-43e4-a0e8-c7755e916276%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
