> > 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 <[email protected]> -- 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/CAEfz%2BTz1DiprvtgeB-ByRcEHZRsLwZF_vOZqoGN-QPY42DMTbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
