Python Package Index Issues

[amcgregor]

Please, please, please auto-hide old versions. They aren't even accessible. It's dubious even uploading a source bundle as the current version can not be used once installed normally without some serious hoop jumping and is a process not documented in the README.

[JdeH]

PyPi isn't functioning properly currently.

These were and are the settings:

Also the download counts have been out for weeks now. I think they recently moved to a new server, but it still doesn't work properly.

[amcgregor]

There's the second issue of the pointless source distribution. Pip installing Transcrypt is a red herring, i.e. it might seem to work, but not work with your version that has yet to incorporate the __main__ / entry_points automatic script generation mechanism. Not including a source distribution would better force potential users to read the documentation.

[JdeH]

Haven't mentioned pip install anywhere to my knowledge.
May come later.

[amcgregor]

It's standard Python package use. The first thing almost anyone will do with a package visible on Pypi is attempt to "pip install" it; again, this seems to be clash against standard Python practices. The commits to move the license stub into the package, rename the main entry point __main__.py and add the console_scripts entry-point have made my fork pip installable. (Later? It's already here! ;)

[JdeH]

I also have some paid work to do, so indeed, it'll have to wait a while...
Note that it's still alpha. Installation issues do not yet have a high prio for me.

[JdeH]

Pip installation merged manually into main branch.

[amcgregor]

Glad that that process seems to work well on Windows; that was my only real concern with using the standard mechanism as I have no Windows to test with. :)