current configuration of Mercurial package in PyPI

[Benoit Boissinot]

On Tue, Jul 16, 2013 at 6:20 PM, FUJIWARA Katsunori
<foozy at lares.dti.ne.jp>wrote:

> Thank you for your alternation of the pypi configuration !
>
> But now, "pip install mercurial" seems to fail with "Could not find
> any downloads" :-<
>
> According to empty "https://pypi.python.org/simple/Mercurial/", it
> seems that there is no release version explicitly uploaded to pypi.


> If so, at least one release (2.6.3, now) should be uploaded to pypi.
>
> Done, but it's quite some pain to do manually... And automating it involve
fixing the casing mismatch (mercurial vs. Mercurial) with setup.py vs PyPI.


> At Mon, 15 Jul 2013 20:53:25 -0400,
> Augie Fackler wrote:
> >
> > (+mercurial-devel)
> >
> > I just altered the pypi configuration for Mercurial from "As above but
> also ask tools to scrape Homepage and Download URL (slow!)" to "Do not
> extract URLs from the long description field - only use URLs explicitly
> specified below and files uploaded to PyPI (this is preferred)."
> >
> > This means (as I understand it) that users will now only get releases
> uploaded to pypi when installing with pip, but also that they won't get
> surprising results or painfully slow installs (or be unable to install when
> selenic.com is down). If people strongly object, speak up, but I think
> this is going to be the only supported mode for pypi in the not too distant
> future.
> >
> > AF
> >
> > On Jul 5, 2013, at 4:59 AM, FUJIWARA Katsunori <foozy at lares.dti.ne.jp>
> wrote:
> >
> > > Hi, Augie and Benoit.
> > >
> > > I assume that your are maintainers of mercurial package in PyPI
> > > site, according to user ID "durin42" and "bboissin" on the page
> > > https://pypi.python.org/pypi/Mercurial.
> > >
> > > Please ignore below and tell me so, if I mistake :-)
> > >
> > > Current PyPI configuration for mercurial seems to:
> > >
> > >  (1) list many links in the index page below, and
> > >
> > >        https://pypi.python.org/simple/Mercurial/
> > >
> > >  (2) cause scraping the download page in selenic.com to find the
> > >      recent one out
> > >
> > >      because some of download_url links in the index page above
> > >      refer not tarball but the download page.
> > >
> > > Then, these seem to cause below:
> > >
> > >  (A) execution of "pip install mercurial" becomes very slow
> > >
> > >      because all links in the index page are examined
> > >
> > >  (B) scraping causes unexpected installation of RC version
> > >
> > >      because tarball of RC version in the download page is
> > >      recognized as recent one, if it exists at that time.
> > >
> > >      actually, I found the tweet of the user who got mercurial
> > >      RC version via "pip install mercurial", and hit the bug
> > >      just fixed in code freeze period (= not yet released) :-<
> > >
> > > According to the person who told me the problem of current PyPI
> > > configuration for mercurial package, the notification about "improving
> > > the speed and reliability of PyPI" has been sent to every maintainers
> > > of packages in PyPI, and it can resolve problems above.
> > >
> > >    http://pypi-externals.caremad.io/help/what/
> > >
> > >    http://www.python.org/dev/peps/pep-0438/
> > >
> > > IMHO, at least, some configuration changes to prevent users from
> > > installing unexpected RC version (2.7-rc will come soon!) should
> > > be done.
> > >
> > > Thanks for your usual maintenance.
> > >
> > > Best regards.
> > >
> > > ----------------------------------------------------------------------
> > > [FUJIWARA Katsunori]                             foozy at lares.dti.ne.jp
> >
> >
>
>
> ----------------------------------------------------------------------
> [FUJIWARA Katsunori]                             foozy at lares.dti.ne.jp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130716/5038ddf5/attachment.html>