[Catalog-sig] PyPI web interface UX (Was: API for uploading packages to PyPI)
techtonik at gmail.com
Fri Mar 22 09:26:25 CET 2013
OMG. I didn't even looked at the boxes. IMHO somebody should reduce the
amount of duplication and choices between menu and boxes. It is
really-really overburdened. For example, no need to say "use search above"
when it is evident the you need to find the button, or to use that "browse
all packages" link when it is actually a first item on the menu.
RSS should be moved out of scope of main menu. It is just "yikes!".
The whole menu section with links to main Python web site should be moved
out of place (is there a quick way to measure how many users follow these
Yes, I can send a patch if everyone agrees.
On Fri, Mar 22, 2013 at 11:16 AM, Ronald Oussoren <ronaldoussoren at mac.com>wrote:
> On 22 Mar, 2013, at 8:37, anatoly techtonik <techtonik at gmail.com> wrote:
> I understand that this will make PyPI a potential target for automated
> spam bots, but still it will be awesome to have an API to upload packages
> to PyPI.
> For example, I have a code that extract all necessary meta data for the
> package from the source file itself. It is even able to generate setup.py
> from this data. https://bitbucket.org/techtonik/astdump The next logical
> step in this chain is to teach it to upload stuff to PyPI.
> Now I thought that this setup.py is an unnecessary complication. What I
> need, ideally is just upload single .py file, or a JSON and a .tar.gz FWIW.
> Is there a straightforward API for things like that?
> Several APIs are documented on pages linked directly from the PyPI
> homepage (the Infrastructure box)
> Please, CC.
> anatoly t.
> Catalog-SIG mailing list
> Catalog-SIG at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalog-SIG