From tarek.ziade at ingeniweb.com Fri Jun 6 17:52:23 2008 From: tarek.ziade at ingeniweb.com (Tarek Ziade) Date: Fri, 6 Jun 2008 17:52:23 +0200 Subject: [Catalog-sig] Problem uploading files at PyPI Message-ID: <a26746990806060852q65abd5fen44f8d0d06180ef03@mail.gmail.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20080606/a3a6239f/attachment.htm> From martin at v.loewis.de Sat Jun 7 10:56:39 2008 From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=) Date: Sat, 07 Jun 2008 10:56:39 +0200 Subject: [Catalog-sig] Problem uploading files at PyPI In-Reply-To: <a26746990806060852q65abd5fen44f8d0d06180ef03@mail.gmail.com> References: <a26746990806060852q65abd5fen44f8d0d06180ef03@mail.gmail.com> Message-ID: <484A4D47.6000602@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 From tarek.ziade at ingeniweb.com Sat Jun 7 11:28:17 2008 From: tarek.ziade at ingeniweb.com (Tarek Ziade) Date: Sat, 7 Jun 2008 11:28:17 +0200 Subject: [Catalog-sig] Problem uploading files at PyPI In-Reply-To: <484A4D47.6000602@v.loewis.de> References: <a26746990806060852q65abd5fen44f8d0d06180ef03@mail.gmail.com> <484A4D47.6000602@v.loewis.de> Message-ID: <a26746990806070228y47c8bd38oae65d3ff4683f600@mail.gmail.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20080607/8f328381/attachment.htm> From ben at groovie.org Tue Jun 10 04:05:39 2008 From: ben at groovie.org (Ben Bangert) Date: Mon, 9 Jun 2008 19:05:39 -0700 Subject: [Catalog-sig] Pypi silliness when finding dev versions Message-ID: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2507 bytes Desc: not available URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20080609/b7cd00aa/attachment.bin> From martin at v.loewis.de Tue Jun 10 06:00:03 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Tue, 10 Jun 2008 06:00:03 +0200 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> Message-ID: <484DFC43.1090407@v.loewis.de> > 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 From ben at groovie.org Tue Jun 10 18:03:37 2008 From: ben at groovie.org (Ben Bangert) Date: Tue, 10 Jun 2008 09:03:37 -0700 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <484DFC43.1090407@v.loewis.de> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> Message-ID: <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2507 bytes Desc: not available URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20080610/419001d7/attachment.bin> From martin at v.loewis.de Tue Jun 10 21:54:49 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Tue, 10 Jun 2008 21:54:49 +0200 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> Message-ID: <484EDC09.7090406@v.loewis.de> > 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 From benji at zope.com Tue Jun 10 22:05:36 2008 From: benji at zope.com (Benji York) Date: Tue, 10 Jun 2008 16:05:36 -0400 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <484EDC09.7090406@v.loewis.de> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> <484EDC09.7090406@v.loewis.de> Message-ID: <e5fff6640806101305n738583d0r84e6795094fdede0@mail.gmail.com> 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 From ben at groovie.org Tue Jun 10 22:13:32 2008 From: ben at groovie.org (Ben Bangert) Date: Tue, 10 Jun 2008 13:13:32 -0700 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <484EDC09.7090406@v.loewis.de> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> <484EDC09.7090406@v.loewis.de> Message-ID: <4BE785C4-B07F-4748-9BEC-E0E99E01BB45@groovie.org> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2507 bytes Desc: not available URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20080610/3ae27c9d/attachment.bin> From martin at v.loewis.de Tue Jun 10 22:24:39 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Tue, 10 Jun 2008 22:24:39 +0200 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <e5fff6640806101305n738583d0r84e6795094fdede0@mail.gmail.com> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> <484EDC09.7090406@v.loewis.de> <e5fff6640806101305n738583d0r84e6795094fdede0@mail.gmail.com> Message-ID: <484EE307.20608@v.loewis.de> > 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 From martin at v.loewis.de Tue Jun 10 22:34:52 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Tue, 10 Jun 2008 22:34:52 +0200 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <4BE785C4-B07F-4748-9BEC-E0E99E01BB45@groovie.org> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> <484EDC09.7090406@v.loewis.de> <4BE785C4-B07F-4748-9BEC-E0E99E01BB45@groovie.org> Message-ID: <484EE56C.4050401@v.loewis.de> > 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. I don't think I have the time to implement such a feature; PyPI does not special-case URL syntaxes. Contributions are welcome. Regards, Martin From jim at zope.com Tue Jun 10 22:15:28 2008 From: jim at zope.com (Jim Fulton) Date: Tue, 10 Jun 2008 16:15:28 -0400 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <484EDC09.7090406@v.loewis.de> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> <484EDC09.7090406@v.loewis.de> Message-ID: <BA0E8506-9E60-4648-9E5C-ABD99454CCC4@zope.com> On Jun 10, 2008, at 3:54 PM, Martin v. L?wis 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? It would be really bad. It's important for old releases to remain visible so that applications that depend on them can find them. A better solution to this problem would be to hide dev releases. Dev releases should never be uploaded to pypi. Jim -- Jim Fulton Zope Corporation From pje at telecommunity.com Wed Jun 11 06:48:56 2008 From: pje at telecommunity.com (Phillip J. Eby) Date: Wed, 11 Jun 2008 00:48:56 -0400 Subject: [Catalog-sig] Pypi silliness when finding dev versions In-Reply-To: <BA0E8506-9E60-4648-9E5C-ABD99454CCC4@zope.com> References: <B1292086-61A4-4462-9286-CDE32C91DCEC@groovie.org> <484DFC43.1090407@v.loewis.de> <2A84F14C-DAF3-40AB-8415-AAC2BC387D8B@groovie.org> <484EDC09.7090406@v.loewis.de> <BA0E8506-9E60-4648-9E5C-ABD99454CCC4@zope.com> Message-ID: <20080611044827.773433A405F@sparrow.telecommunity.com> At 04:15 PM 6/10/2008 -0400, Jim Fulton wrote: >A better solution to this problem would be to hide dev releases. Dev >releases should never be uploaded to pypi. This is about dev *links*, not dev releases.