Richard Jones | 3 Nov 23:19 2005
Picon

Re: [lfini <at> arcetri.astro.it: cannot submit a package]

On Fri, 28 Oct 2005 08:30 am, Jean-Paul Calderone wrote:
> I've had the described problem when trying to update a project and not
> having sufficient permissions to do so.  The interface gives no indication
> that this is the case, since it is just a standard HTTP auth dialog.

There should be an explanation when the auth fails (unless you're using 
Safari, which doesn't display the content of auth failure pages).

> The 
> issue is conflated by the fact that sometimes (all the time?), after doing
> this, your old credentials are dropped and you have to log back in as
> yourself.

We're using HTTP Basic Auth. I see no reason (apart from some setting in your 
browser) why credentials would be dropped.

     Richard
_______________________________________________
Catalog-sig mailing list
Catalog-sig <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Jean-Paul Calderone | 4 Nov 00:18 2005

Re: [lfini <at> arcetri.astro.it: cannot submit a package]

On Fri, 4 Nov 2005 09:19:55 +1100, Richard Jones <richardjones <at> optushome.com.au> wrote:
>On Fri, 28 Oct 2005 08:30 am, Jean-Paul Calderone wrote:
>> I've had the described problem when trying to update a project and not
>> having sufficient permissions to do so.  The interface gives no indication
>> that this is the case, since it is just a standard HTTP auth dialog.
>
>There should be an explanation when the auth fails (unless you're using
>Safari, which doesn't display the content of auth failure pages).
>

I'm not and there isn't.

>
>> The
>> issue is conflated by the fact that sometimes (all the time?), after doing
>> this, your old credentials are dropped and you have to log back in as
>> yourself.
>
>We're using HTTP Basic Auth. I see no reason (apart from some setting in your
>browser) why credentials would be dropped.
>

I haven't modified any settings in Firefox that I am aware of that relate to this.

Jean-Paul
Stefane Fermigier | 8 Nov 12:41 2005

UTF8 bug on cheeseshop

The cheeseshop main page claims to be UTF-8:

   <?xml version="1.0" encoding="utf-8"?>

But there are currently non-utf-8 encoded latin-1:

   <tr class="even">
     <td><a href="/pypi/pycompta/0.3.1">pycompta&nbsp;0.3.1</a></td>
     <td>comptabilité d'entreprise</td>
   </tr>

This confuses strict XML parsers (like lxml).

   S.

--

-- 
Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile).
Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps
Gestion de contenu web / portail collaboratif / groupware / open source!
"Martin v. Löwis" | 8 Nov 19:54 2005
Picon

Re: UTF8 bug on cheeseshop

Stefane Fermigier wrote:
> The cheeseshop main page claims to be UTF-8:
> 
>    <?xml version="1.0" encoding="utf-8"?>
> 
> But there are currently non-utf-8 encoded latin-1:
> 
>    <tr class="even">
>      <td><a href="/pypi/pycompta/0.3.1">pycompta&nbsp;0.3.1</a></td>
>      <td>comptabilité d'entreprise</td>
>    </tr>

What URL are you accessing? I cannot reproduce the problem;
it encodes the character just fine in UTF-8 for me.

Regards,
Martin
Grig Gheorghiu | 9 Nov 22:33 2005
Picon

Standardized way of getting to a package download URL in Cheeseshop

I'm working on a project I called "Cheesecake" which aims to quantify
the "goodness" of Python packages based on various indicators such as
presence of special files (README, LICENSE, etc.), special directories
(tests, doc, etc.), percentage of modules/classes/methods/functions
with docstrings, etc.

It would be nice if there was a standardized way to get to a download
URL for a given package listed at the Cheeseshop. Currently some
packages are hosted there, some are hosted elsewhere, but in any case
one would think that a pointer to the full URL for the package file
could be kept on the Cheeseshop page for that package and made
available via an API.

I'd volunteer to start this ball rolling if nobody else has been
working on it. What is the procedure for contributing to the PyPI
project?

Grig
"Martin v. Löwis" | 9 Nov 22:47 2005
Picon

Re: Standardized way of getting to a package download URL in Cheeseshop

Grig Gheorghiu wrote:
> It would be nice if there was a standardized way to get to a download
> URL for a given package listed at the Cheeseshop. Currently some
> packages are hosted there, some are hosted elsewhere, but in any case
> one would think that a pointer to the full URL for the package file
> could be kept on the Cheeseshop page for that package and made
> available via an API.

The challenge here is that for packages with no downloadable files,
it is difficult to infer a URL from the metadata. There is a download
URL, but it is imprecise, as there is only a single one, not multiple
download URLs depending on type of package to download.

So different packages use different strategies, such as only
giving the base URL, and expecting the user to actually read
the page at the download URL to understand where the package
proper is available.

> I'd volunteer to start this ball rolling if nobody else has been
> working on it. What is the procedure for contributing to the PyPI
> project?

Depends on the nature of the change you propose: for a change
in the meta-data, you need to write a PEP, and provide patches to
distutils.

Regards,
Martin
Grig Gheorghiu | 9 Nov 23:02 2005
Picon

Re: Standardized way of getting to a package download URL in Cheeseshop

--- "Martin v. Löwis" <martin <at> v.loewis.de> wrote:

> Grig Gheorghiu wrote:
> > It would be nice if there was a standardized way to get to a
> download
> > URL for a given package listed at the Cheeseshop. Currently some
> > packages are hosted there, some are hosted elsewhere, but in any
> case
> > one would think that a pointer to the full URL for the package file
> > could be kept on the Cheeseshop page for that package and made
> > available via an API.
> 
> The challenge here is that for packages with no downloadable files,
> it is difficult to infer a URL from the metadata. There is a download
> URL, but it is imprecise, as there is only a single one, not multiple
> download URLs depending on type of package to download.
> 
> So different packages use different strategies, such as only
> giving the base URL, and expecting the user to actually read
> the page at the download URL to understand where the package
> proper is available.
> 

You're right, I can see how it would be more difficult to keep track of
multiple download URLs per package, one for each type of package such
as .tgz, .zip etc. 

The situation is also made more difficult by the fact that some
packages are hosted at Source Forge, which means that their download
URL is picked up dynamically based on user preferences for the mirrors.
(Continue reading)

Ian Bicking | 9 Nov 23:05 2005

Re: Standardized way of getting to a package download URL in Cheeseshop

Grig Gheorghiu wrote:
> It would be nice if there was a standardized way to get to a download
> URL for a given package listed at the Cheeseshop. Currently some
> packages are hosted there, some are hosted elsewhere, but in any case
> one would think that a pointer to the full URL for the package file
> could be kept on the Cheeseshop page for that package and made
> available via an API.

There's a not-exactly-standard way to download a package in setuptools, 
i.e., the algorithm easy_install uses to find packages.  You could grab 
the function out of there (I can't remember where it is, but it 
shouldn't be too hard to find).  You might want to copy it out and add 
extra information so you can score the download availability, since it 
finds some links that are deeper and further from the PyPI record than 
they should be (and they should lose points for that).

--

-- 
Ian Bicking  /  ianb <at> colorstudy.com  /  http://blog.ianbicking.org
Phillip J. Eby | 9 Nov 23:09 2005

Re: Standardized way of getting to a package download URL in Cheeseshop

At 01:33 PM 11/9/2005 -0800, Grig Gheorghiu wrote:
>I'm working on a project I called "Cheesecake" which aims to quantify
>the "goodness" of Python packages based on various indicators such as
>presence of special files (README, LICENSE, etc.), special directories
>(tests, doc, etc.), percentage of modules/classes/methods/functions
>with docstrings, etc.
>
>It would be nice if there was a standardized way to get to a download
>URL for a given package listed at the Cheeseshop.

setuptools' "package_index" module has facilities to scan Cheeseshop pages 
and the pages they link to for URLs that are downloadable 
distributions.  Also, the "easy_install" command-line tool can be used to 
fetch and extract editable source (or check out from subversion) the source 
code of a project.  For example:

     $ easy_install -eb~/projects SQLObject
     Searching for SQLObject
     Reading http://www.python.org/pypi/SQLObject/
     Reading http://sqlobject.org
     Best match: SQLObject 0.7.0
     Downloading 
http://cheeseshop.python.org/packages/source/S/SQLObject/SQLObject-0.7.0.tar.gz#md5=dccb921b5df6a15312b56630ac4ac205
     Processing SQLObject-0.7.0.tar.gz

     Extracted editable version of SQLObject to ~/projects/sqlobject

Notice that this works even with projects not hosted at the Cheeseshop, 
even if they are on Sourceforge mirrors:

(Continue reading)

Grig Gheorghiu | 9 Nov 23:16 2005
Picon

Re: Standardized way of getting to a package download URL in Cheeseshop

--- "Phillip J. Eby" <pje <at> telecommunity.com> wrote:

> At 01:33 PM 11/9/2005 -0800, Grig Gheorghiu wrote:
> >I'm working on a project I called "Cheesecake" which aims to
> quantify
> >the "goodness" of Python packages based on various indicators such
> as
> >presence of special files (README, LICENSE, etc.), special
> directories
> >(tests, doc, etc.), percentage of modules/classes/methods/functions
> >with docstrings, etc.
> >
> >It would be nice if there was a standardized way to get to a
> download
> >URL for a given package listed at the Cheeseshop.
> 
> setuptools' "package_index" module has facilities to scan Cheeseshop
> pages 
> and the pages they link to for URLs that are downloadable 
> distributions.  Also, the "easy_install" command-line tool can be
> used to 
> fetch and extract editable source (or check out from subversion) the
> source 
> code of a project.  For example:
> 
>      $ easy_install -eb~/projects SQLObject
>      Searching for SQLObject
>      Reading http://www.python.org/pypi/SQLObject/
>      Reading http://sqlobject.org
>      Best match: SQLObject 0.7.0
(Continue reading)


Gmane