I’m currently planning a first ‘alpha’ release of MySQL Connector/Python, but I’m now doubting whether the naming and installation of the module is actually good.

Currently, the module lives, in site-packages/mysql/connector/, or import mysql.connector. Since this is an official MySQL, sorry, Sun Microsystems, project, I thought that the ‘parent’ module mysql would be good enough.

But is it? Would it break your modules with the same name?

The idea was to make more tools for Python and have them all under the mysql module, but maybe we need a smarter name for this? Maybe sunmysql/connector?

Comments are welcome! You can also email me directly (if you can figure out the cryptic anti-spam): geert_dot_vanderkelen_APETAIL_sun_dot_com.

Comments

LenZ: Mon Nov 9 2009, 16:42

Hi Geert! I think using the “mysql” name space is the appropriate thing to do. In the end, it's the name of the product you want to connect to, the name of the company behind it probably does not matter :)
Bryan Alsdorf: Mon Nov 9 2009, 23:32

I think your current module is good. I need to check this project out, I keep reading about it but haven't had a chance to use it yet.

I am slowly becoming a python snob, wish I had written Eventum in it…