Home > MySQL, Python, Work > Naming a Python package for distribution?

Naming a Python package for distribution?

August 3rd, 2012 Leave a comment Go to comments

I’m currently figuring out how to name the MySQL Connector/Python distributions so it works well with PyPi. Source archives would be named like mysql-connector-python-X.Y.Z.tar.gz.

The ‘name’ metadata would be ‘MySQL Connector Python’, thus without any underscores or dashes. This works OK, but if people have objections, please leave a comment.

  1. Medardo Rodriguez
    August 4th, 2012 at 02:37 | #1

    python-merchise-mysql-connector-X.Y.Z.tar.gz

    Where I write “merchise” use your enterprise name.

    • August 4th, 2012 at 06:46 | #2

      Thanks Medardo, however, ‘mysql’ is the ‘enterprise’ name (of sorts) and we are trying to keep consistent with our other connectors like ‘mysql-connector-j’ and ‘mysql-connector-odbc’.

  2. Lennart Regebro
    August 4th, 2012 at 07:34 | #3

    Including “python” is unecessary from PyPI’s point of view. Otherwise mysql-connector-python-X.Y.Z.tar.gz is fine.

  3. Valeriy
    August 5th, 2012 at 19:44 | #4

    .tar.gz file name is OK. I wonder why not to use MySQL Connector/Python though, as for all other connectors?

    • August 7th, 2012 at 09:02 | #5

      MySQL Connector/Python is indeed the official name. We’ve settled with ‘mysql-connector-python’ in the meta data, since eventually, that is how package will be named. It’s magically being renamed with dashes anyways, but explicit is better.