Tarek Ziade | 6 Jun 17:52 2008

Problem uploading files at PyPI

Hello,

I have some problems to upload a particular egg at PyPI

...
Using PyPI login from /Users/tziade/.pypirc
Submitting dist/iw.rotatezlogs-0.1.1.tar.gz to http://pypi.python.org/pypi
Upload failed (500): There's been a problem with your request
Submitting dist/iw.rotatezlogs-0.1.1-py2.4.egg to http://pypi.python.org/pypi
Upload failed (500): There's been a problem with your request

This package seem fine, the email is corresponding to the right PyPI user,
so I was wondering if this is not a specific server-side issue.

Regards
Tarek


--
Tarek Ziadé - Directeur Technique
INGENIWEB (TM) - SAS 50000 Euros - RC B 438 725 632
Bureaux de la Colline - 1 rue Royale - Bâtiment D - 9ème étage
92210 Saint Cloud - France
Phone : 01.78.15.24.00 / Fax : 01 46 02 44 04
http://www.ingeniweb.com - une société du groupe Alter Way

_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
"Martin v. Löwis" | 7 Jun 10:56 2008
Picon

Re: Problem uploading files at PyPI

> This package seem fine, the email is corresponding to the right PyPI user,
> so I was wondering if this is not a specific server-side issue.

The problem is (apparently) an invalid classifier. Your package version
was not registered, so file upload tried to transparently register it,
which then choked as it couldn't find one of the classifiers in the
database. I added a validation step now before the actual package
registration, so you should get a more meaningful error message now.

HTH,
Martin
Tarek Ziade | 7 Jun 11:28 2008

Re: Problem uploading files at PyPI

Yes, I found a typo in one classifier, the error message in that case looks great now,

Thank you !

Tarek

2008/6/7 "Martin v. Löwis" <martin <at> v.loewis.de>:
> This package seem fine, the email is corresponding to the right PyPI user,
> so I was wondering if this is not a specific server-side issue.

The problem is (apparently) an invalid classifier. Your package version
was not registered, so file upload tried to transparently register it,
which then choked as it couldn't find one of the classifiers in the
database. I added a validation step now before the actual package
registration, so you should get a more meaningful error message now.

HTH,
Martin



--
Tarek Ziadé - Directeur Technique
INGENIWEB (TM) - SAS 50000 Euros - RC B 438 725 632
Bureaux de la Colline - 1 rue Royale - Bâtiment D - 9ème étage
92210 Saint Cloud - France
Phone : 01.78.15.24.00 / Fax : 01 46 02 44 04
http://www.ingeniweb.com - une société du groupe Alter Way
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Ben Bangert | 10 Jun 04:05 2008

Pypi silliness when finding dev versions

It'd be really great if I didn't have to go back through 20-some  
descriptions that Cheeseshop has on hand for Pylons, just to remove  
the dead Pylons-dev egg link, which is still found regardless of the  
latest description here:
http://pypi.python.org/simple/Pylons/

It took me about 20-some minutes to go through all the Routes releases  
on cheeseshop and fix the link for Routes-dev to work properly, am I  
looking at something even worse, or is there a faster way to get this  
page fixed so that Pylons-dev only is linked in once (to the latest  
destination in the latest release).

Cheers,
Ben
Attachment (smime.p7s): application/pkcs7-signature, 3388 bytes
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
"Martin v. Löwis" | 10 Jun 06:00 2008
Picon

Re: Pypi silliness when finding dev versions

> It'd be really great if I didn't have to go back through 20-some
> descriptions that Cheeseshop has on hand for Pylons, just to remove the
> dead Pylons-dev egg link, which is still found regardless of the latest
> description here:
> http://pypi.python.org/simple/Pylons/
> 
> It took me about 20-some minutes to go through all the Routes releases
> on cheeseshop and fix the link for Routes-dev to work properly, am I
> looking at something even worse, or is there a faster way to get this
> page fixed so that Pylons-dev only is linked in once (to the latest
> destination in the latest release).

Unfortunately, I cannot understand your message: What is the Pylons-dev
egg link, why is it dead, and why do you think you have to go back
20-some descriptions (which ones)?

I can only see a single link that might be the Pylons-dev egg link,
namely

https://www.knowledgetap.com/hg/pylons-dev/archive/tip.tar.gz#egg=Pylons-dev

and it doesn't appear to be dead, and I don't see 20 different releases
of Pylons, only 8 (0.9.2, 0.9.3, 0.9.4, 0.9.4.1, 0.9.5, 0.9.6, 0.9.6.1,
0.9.6.2).

Also, why do you want to remove a link from the pages?

Regards,
Martin
Ben Bangert | 10 Jun 18:03 2008

Re: Pypi silliness when finding dev versions

On Jun 9, 2008, at 9:00 PM, Martin v. Löwis wrote:
> Unfortunately, I cannot understand your message: What is the Pylons- 
> dev
> egg link, why is it dead, and why do you think you have to go back
> 20-some descriptions (which ones)?
>
> I can only see a single link that might be the Pylons-dev egg link,
> namely
>
> https://www.knowledgetap.com/hg/pylons-dev/archive/ 
> tip.tar.gz#egg=Pylons-dev

Yes, this is because the co-founder of the project has already gone  
through all of the releases, and removed all the other #egg=Pylons-dev  
links from them.

Here is one that I have yet to go back through and remove the old  
#egg=Pylons-dev links from:
http://pypi.python.org/simple/Beaker/

At the bottom, you can see multiple links for it. When easy_install  
runs, it usually goes for the first link (which is from an old package  
description), not the one from the latest package.

> Also, why do you want to remove a link from the pages?

Because there is only one development version, and the repo changed  
from where it was in the past. So the old links are totally dead and  
shouldn't be looked at. #egg=Beaker-dev should be a unique name, and  
there shouldn't be multiple links for it in the page there which is  
what easy_install looks at when you do:
easy_install -U Beaker==dev

Cheers,
Ben
Attachment (smime.p7s): application/pkcs7-signature, 3388 bytes
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
"Martin v. Löwis" | 10 Jun 21:54 2008
Picon

Re: Pypi silliness when finding dev versions

> At the bottom, you can see multiple links for it. When easy_install
> runs, it usually goes for the first link (which is from an old package
> description), not the one from the latest package.

The simple API shows all links from all packages, not just from the
latest package.

In this case, it would help if PyPI would hide all URLs belonging to
hidden releases.

Would that be desirable?

Phillip?

Regards,
Martin
Benji York | 10 Jun 22:05 2008

Re: Pypi silliness when finding dev versions

On Tue, Jun 10, 2008 at 3:54 PM, "Martin v. Löwis" <martin <at> v.loewis.de> wrote:
>> At the bottom, you can see multiple links for it. When easy_install
>> runs, it usually goes for the first link (which is from an old package
>> description), not the one from the latest package.
>
> The simple API shows all links from all packages, not just from the
> latest package.
>
> In this case, it would help if PyPI would hide all URLs belonging to
> hidden releases.
>
> Would that be desirable?

Nope.  Say a project uses the simple API in their setuptools find-links
setting with version numbers specified in their setup.py (or
buildout.cfg).  If the download URL is hidden when a new release is
made, it would mean that setuptools won't be able to find the older
version when it needs to download it.

This is (or was) the behavior of the "non-simple" pages, and it meant
that maintainers would have to unhide older versions after uploading a
newer one so other people who depend on older versions could continue to
download them.
--

-- 
Benji York
Senior Software Engineer
Zope Corporation
Ben Bangert | 10 Jun 22:13 2008

Re: Pypi silliness when finding dev versions

On Jun 10, 2008, at 12:54 PM, Martin v. Löwis wrote:

> The simple API shows all links from all packages, not just from the
> latest package.
>
> In this case, it would help if PyPI would hide all URLs belonging to
> hidden releases.
>
> Would that be desirable?

As Benji states, that's not desirable. What should happen, is that the  
name after an #egg= link should be unique, and if there's duplicates,  
only the most recent one is put in the Simple page.

Cheers,
Ben
Attachment (smime.p7s): application/pkcs7-signature, 3388 bytes
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
"Martin v. Löwis" | 10 Jun 22:24 2008
Picon

Re: Pypi silliness when finding dev versions

> This is (or was) the behavior of the "non-simple" pages

It is still.

> and it meant
> that maintainers would have to unhide older versions after uploading a
> newer one so other people who depend on older versions could continue to
> download them.

Correct.

So if that is not desirable, then yes, you have to go through all old
releases if you want a link to disappear from the list of URLs available
for the package.

Alternatively, you can delete all old releases, rather than just hiding
them, which also makes the links go away (along with any files that you
may have uploaded).

Regards,
Martin

Gmane