flit register, check closes names.

[Carreau]

I already do that here:

https://github.com/Carreau/PipCreate/blob/master/pipcreate/pipcreate.py#L66-L78

Might need a (weekly) cache for speed ?

[takluyver]

I think it makes more sense to do this when creating the package than registering it, and it's really outside what flit init does - that's for adding flit.ini to an already created package more than creating a package from scratch.

The more I think about this, though, the more I think there's room for a tool to set up packages without taking a one-size-fits-all approach. There's a lot of places where one tool has a majority, but some people will use alternatives, or not want to set that feature up at all:

• Distribution mechanism (setuptools, plain distutils, flit)
• Version control (git, hg, even svn)
• VCS hosting (Github, Bitbucket, Gitorious, self hosted...)
• Tests (py.test, nose)
• CI
• Docs

I'm going to try to put together a prototype.