Am 29.03.2011 19:20 schrieb Jannico: > What, I think, would be required is to name > > CherryPy-3.2.0-py2.win32.exe and CherryPy-3.2.0-py3.win32.exe > ... to ... > CherryPy-3.2.0.win32-py2.3.exe and CherryPy-3.2.0.win32-py3.0.exe
I think you're completely right with that and have already posted this problem on the CherryPy mailing list; I hope they fix it on PyPI.
The reason why it had worked for me was that I was using the 64bit version of Python 2.6 (for which there is no .exe available so the source package gets installed, which works fine). When I just tried it with 32bit Python, I saw the same problem you were reporting.
-- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
