astropy != AstroPy ???

[mdboom]

Is there a good reason for the distutils/setuptools/egg name being different from the Python package name? It's currently defined as "AstroPy" in the setup.py.

Maybe this doesn't matter (sorry to be pedantic), but I find this confusing for the following reasons:

1. I use a tool that cleans my virtualenv by deleting packages by name -- if its name on disk is different from how it's imported I have to remember which is which

2. "pip install AstroPy" someday will confuse people

3. tarballs and installers built with distutils won't match the name of the git repository

[phn]

Hello,

The command pip install astropy will work even if the module is named "AstroPy".

Prasanth

[eteq]

I've seen this in other packages, and it doesn't seem to present too many problems... As Prasanth says various tools seem to generally be able to figure it out.

But having said that, the no really good reason for the capitalized form, either. So I see your point that it makes sense to change the name to astropy so that it's all the same regardless.

As long as there are no objections, I'll just go ahead and change the name in setup.py from AstroPy to astropy

[eteq]

Fixed in commit cb58b73