Upload releases to PyPI for compatibility with new pip versions

[jodal]

As of pip 1.4, the installer prints warnings when installing ws4py since it is downloaded from another server than PyPI:

$ pip --version
pip 1.4 from .../lib/python2.7/site-packages (python 2.7)
$ pip install ws4py
Downloading/unpacking ws4py
  You are installing a potentially insecure and unverifiable file. Future versions of pip will default to disallowing insecure files.
  Downloading ws4py-0.2.4.tar.gz
  Storing download in cache at /tmp/pip-cache/http%3A%2F%2Fwww.defuze.org%2Foss%2Fws4py%2Fws4py-0.2.4.tar.gz
  Running setup.py egg_info for package ws4py

Installing collected packages: ws4py
  Running setup.py install for ws4py

Successfully installed ws4py
Cleaning up...

In pip 1.5 installation of packages not hosted on PyPI will be prevented by default, forcing the user to add the --allow-external ws4py flag to the pip command. Simulating pip 1.5 behavior with flags to pip 1.4:

$ pip install --no-allow-external --no-allow-insecure ws4py
Downloading/unpacking ws4py
  Could not find any downloads that satisfy the requirement ws4py
  Some externally hosted files were ignored (use --allow-external ws4py to allow).
Cleaning up...
No distributions at all found for ws4py
Storing complete log in .../.pip/pip.log

Quoting the changelog for pip 1.4:

pip will now warn when installing a file that is either hosted externally to the index or cannot be verified with a hash. In the future pip will default to not installing them and will require the flags –allow-external NAME, and –allow-insecure NAME respectively. (Pull #985)

IMHO, the best way to solve this is to upload all ws4py releases to the PyPI servers.

[Lawouach]

That's the best way indeed but I'm rather annoyed that pip introduced such a strong requirement. I'll probably move packages to PyPI at some point.

[Lawouach]

Okay so I will now upload ws4py distributions to the main PyPi index from now on. Starting with the 0.3.2 release.