On 28 August 2014 19:58, Donald Stufft don...@stufft.io wrote:
To fix this I'm going to modify PyPI so that it uses the normalized name in
the /simple/ URL and redirects everything else to the non-normalized name.
I'm also going to submit a PR to bandersnatch so that it will use normalized
On 30 September 2014 15:25, Paul Moore p.f.mo...@gmail.com wrote:
On 28 August 2014 19:58, Donald Stufft don...@stufft.io wrote:
To fix this I'm going to modify PyPI so that it uses the normalized name in
the /simple/ URL and redirects everything else to the non-normalized name.
I'm also
On Sep 30, 2014, at 11:14 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 30 September 2014 15:25, Paul Moore p.f.mo...@gmail.com wrote:
On 28 August 2014 19:58, Donald Stufft don...@stufft.io wrote:
To fix this I'm going to modify PyPI so that it uses the normalized name in
the /simple/ URL
On Mon, Sep 01, 2014 at 19:07 -0400, Donald Stufft wrote:
On Sep 1, 2014, at 4:53 PM, holger krekel hol...@merlinux.eu wrote:
On Thu, Aug 28, 2014 at 14:58 -0400, Donald Stufft wrote:
Right now the “canonical” page for a particular project on PyPI is
whatever the
author happened to
On Sep 2, 2014, at 5:36 AM, holger krekel hol...@merlinux.eu wrote:
On Mon, Sep 01, 2014 at 19:07 -0400, Donald Stufft wrote:
On Sep 1, 2014, at 4:53 PM, holger krekel hol...@merlinux.eu wrote:
On Thu, Aug 28, 2014 at 14:58 -0400, Donald Stufft wrote:
Right now the “canonical” page for a
On Thu, Aug 28, 2014 at 14:58 -0400, Donald Stufft wrote:
Right now the “canonical” page for a particular project on PyPI is whatever
the
author happened to name their package (e.g. Django). This requires PyPI to
have
some smarts so that it can redirect things like /simple/django/ to
On Sep 1, 2014, at 4:53 PM, holger krekel hol...@merlinux.eu wrote:
On Thu, Aug 28, 2014 at 14:58 -0400, Donald Stufft wrote:
Right now the “canonical” page for a particular project on PyPI is whatever
the
author happened to name their package (e.g. Django). This requires PyPI to
have
FWIW, as a community member it doesn't seem unreasonable to me to
expect that a certain amount of advance notice be given for changes
like this, *especially* given that the tools are undocumented.
Also, there's a difference between notifying people and running it
by people (for permission). I
I don't know exactly. I'd say a change that in your judgment you
think has a non-trivial chance of breaking existing tools. Holger is
probably in a better position to say. I was just speaking in support
of his request, which seemed reasonable to me.
--Chris
On Mon, Sep 1, 2014 at 5:03 PM,
On Mon, Sep 1, 2014, at 08:15 PM, Chris Jerdonek wrote:
I don't know exactly. I'd say a change that in your judgment you
think has a non-trivial chance of breaking existing tools. Holger is
probably in a better position to say. I was just speaking in support
of his request, which seemed
On Mon, Sep 1, 2014 at 7:15 PM, Donald Stufft don...@stufft.io wrote:
On Mon, Sep 1, 2014, at 08:15 PM, Chris Jerdonek wrote:
I don't know exactly. I'd say a change that in your judgment you
think has a non-trivial chance of breaking existing tools. Holger is
probably in a better position to
On 2 September 2014 12:54, Chris Jerdonek chris.jerdo...@gmail.com wrote:
On Mon, Sep 1, 2014 at 7:15 PM, Donald Stufft don...@stufft.io wrote:
I already give notice (and discussion, often times even PEPs) for any
change
that I believe to be breaking. Wanting more is wanting notice on every
Ah, I didn't think of that- good point. +1 to your suggested approach.
On Thu, Aug 28, 2014 at 3:41 PM, Donald Stufft don...@stufft.io wrote:
Since pip 1.4 it does yes, however the problem here is that typically
bandersnatch
mirrors are simply hosted by plain static web servers and don’t
Right now the “canonical” page for a particular project on PyPI is whatever the
author happened to name their package (e.g. Django). This requires PyPI to have
some smarts so that it can redirect things like /simple/django/ to
/simple/Django/ otherwise someone doing ``pip install django`` would
On Aug 28, 2014, at 2:58 PM, Donald Stufft don...@stufft.io wrote:
Right now the “canonical” page for a particular project on PyPI is whatever
the
author happened to name their package (e.g. Django). This requires PyPI to
have
some smarts so that it can redirect things like
On Aug 28, 2014, at 6:09 PM, Donald Stufft don...@stufft.io wrote:
On Aug 28, 2014, at 2:58 PM, Donald Stufft don...@stufft.io
mailto:don...@stufft.io wrote:
Right now the “canonical” page for a particular project on PyPI is whatever
the
author happened to name their package (e.g.
Since pip 1.4 it does yes, however the problem here is that typically
bandersnatch
mirrors are simply hosted by plain static web servers and don’t require any
sort of runtime logic.
On Aug 28, 2014, at 6:39 PM, Joe Smith yasumo...@gmail.com wrote:
Naive question- does pip send over a
Naive question- does pip send over a UserAgent (or something) that contains
a version number the server can use to determine which behavior to default
to?
That would allow a deprecation cycle of N months or so that will let people
upgrade from 1.5 to 1.6. We could then watch usage of 1.5 decrease
On 29 Aug 2014 08:27, Donald Stufft don...@stufft.io wrote:
Just thought of this, if the normalized name doesn’t match the real
name,
then add entries for both. This will make it so that pip 1.5 continues to
work
and pip 1.6+.
Having bandersnatch mirrors publish under both names sounds like
19 matches
Mail list logo
