Re: [Python-Dev] Yearly PyPI breakage

2016-05-06 Thread Donald Stufft
> On May 6, 2016, at 1:11 PM, A.M. Kuchling wrote: > > On Thu, May 05, 2016 at 10:31:48PM -0400, Donald Stufft wrote: >> I don't believe we've ever told someone that something can't happen because >> of >> Warehouse, only that *I* won't implement something until after Warehouse. >> That >> oft

Re: [Python-Dev] Yearly PyPI breakage

2016-05-06 Thread A.M. Kuchling
On Thu, May 05, 2016 at 10:31:48PM -0400, Donald Stufft wrote: > I don't believe we've ever told someone that something can't happen because of > Warehouse, only that *I* won't implement something until after Warehouse. That > often times means that something won't happen until after Warehouse beca

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Donald Stufft
> On May 5, 2016, at 8:35 PM, David Wilson wrote: > > On Fri, May 06, 2016 at 12:03:48AM +, Brett Cannon wrote: > >>Is there something to contemplate in here? I dislike posting questions >>instead of answers, but it seems apparent there is a problem here and it >>continues to re

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Stefan Krah
Brett Cannon python.org> writes: > This is whole thread is off-topic precisely because all of this is discussed -- in the open -- on distutils-sig and decided there. If people feel changes need to be made like broadcasting to a wider audience when a change occurs, then please bring it up on distut

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread David Wilson
On Fri, May 06, 2016 at 12:03:48AM +, Brett Cannon wrote: > Is there something to contemplate in here? I dislike posting questions > instead of answers, but it seems apparent there is a problem here and it > continues to remain unaddressed. > This is whole thread is off-topic prec

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Stefan Krah
Donald Stufft stufft.io> writes: > > Technically, he > > didn't gloat, but suddenly legal advice was apparently readily available. > > > > https://pypi.python.org/pypi/m3-cdecimal > > > > I'm not going to respond to the rest of this, because I don't think it's > possible for you and me to have

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Brett Cannon
On Thu, 5 May 2016 at 16:00 Mark Lawrence via Python-Dev < python-dev@python.org> wrote: > On 05/05/2016 23:22, Stefan Krah wrote > > > > Fredrik Lundh is also affected (and might not have received any mail, > > same as me): > > > > https://pypi.python.org/pypi/PIL > > > > He might be, but clear

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Brett Cannon
On Thu, 5 May 2016 at 16:54 David Wilson wrote: > This is mostly just observational, and not meant primarily as criticism > of the fabulous work of Donald and others (ignoring pypa, also the > prompt, reliable, and skilled support responses common on such places as > IRC), however I can't help bu

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread David Wilson
This is mostly just observational, and not meant primarily as criticism of the fabulous work of Donald and others (ignoring pypa, also the prompt, reliable, and skilled support responses common on such places as IRC), however I can't help but notice that PyPI governance seems to come under fire vas

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Mark Lawrence via Python-Dev
On 06/05/2016 00:06, Barry Warsaw wrote: On May 05, 2016, at 11:58 PM, Mark Lawrence via Python-Dev wrote: On 05/05/2016 23:22, Stefan Krah wrote Fredrik Lundh is also affected (and might not have received any mail, same as me): https://pypi.python.org/pypi/PIL Maybe, but then there's th

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Stefan Krah
Chris Barker noaa.gov> writes: > Indeed -- Fredrik never made any effort to support pypi, pip, etc. -- that's why the Pillow fork was started in the first place. Maybe, but he created PIL, so thank you, Fredrik! Stefan Krah ___ Python-Dev mailing lis

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Donald Stufft
> On May 5, 2016, at 6:22 PM, Stefan Krah wrote: > > Nick Coghlan gmail.com> writes: >> I know you're not happy with myself and the other distutils-sig folks >> regarding the decision to deprecate and remove automatic link >> spidering, > > More accurately: Not happy with the removal of the ch

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Barry Warsaw
On May 05, 2016, at 11:58 PM, Mark Lawrence via Python-Dev wrote: >On 05/05/2016 23:22, Stefan Krah wrote >> >> Fredrik Lundh is also affected (and might not have received any mail, >> same as me): >> >> https://pypi.python.org/pypi/PIL Maybe, but then there's the friendly fork: https://pypi.p

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Chris Barker
> > Fredrik Lundh is also affected (and might not have received any mail, >> same as me): >> >> https://pypi.python.org/pypi/PIL >> >> > He might be, but clearly the Python community as a whole is not impacted. > From what I see the latest version of PIL that is available is 1.1.6, which > requir

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Mark Lawrence via Python-Dev
On 05/05/2016 23:22, Stefan Krah wrote Fredrik Lundh is also affected (and might not have received any mail, same as me): https://pypi.python.org/pypi/PIL He might be, but clearly the Python community as a whole is not impacted. From what I see the latest version of PIL that is available

Re: [Python-Dev] Yearly PyPI breakage

2016-05-05 Thread Stefan Krah
Nick Coghlan gmail.com> writes: > I know you're not happy with myself and the other distutils-sig folks > regarding the decision to deprecate and remove automatic link > spidering, More accurately: Not happy with the removal of the checksummed "explicit" mode. What I would have preferred is a Fre

Re: [Python-Dev] Yearly PyPI breakage

2016-05-04 Thread Nick Coghlan
On 4 May 2016 at 13:44, wrote: >> >> (Is cdecimal substantially different from the _decimal added in 3.5?) >> > AFAICT, they are unrelated codebases that do about the same thing with the > same amount of performance, with the main exception that _decimal in 3.5 does > not require one to change

Re: [Python-Dev] Yearly PyPI breakage

2016-05-04 Thread Nick Coghlan
On 4 May 2016 at 05:06, Stefan Krah wrote: > > Hello, > > Could someone enlighten me which hoops I have to jump through > this year in order to keep pip downloads working? Stefan, I know you're not happy with myself and the other distutils-sig folks regarding the decision to deprecate and remove

Re: [Python-Dev] Yearly PyPI breakage

2016-05-04 Thread Glyph
On May 3, 2016, at 9:15 PM, Stefan Krah wrote: > >> [cut overlong post] > > Glyph, > > nice sneaky way to try to divert from the original issue. The original issue, as I understood it, at the start of the thread was "which hoops I have to jump through this year in order to keep pip downloads

Re: [Python-Dev] Yearly PyPI breakage

2016-05-04 Thread Stefan Krah
sdamon.com> writes: > You posted a mean-spirited complaint about a policy that is nearly exactly > two years old, to the wrong list, and call out the people calmly trying to > explain what happened and why, and how you can mitigate it for your own work Yeah, right. This is distutils-sig level.

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread tritium-list
on-dev-bounces+tritium- > list=sdamon@python.org] On Behalf Of Stefan Krah > Sent: Wednesday, May 04, 2016 00:15 > To: python-dev@python.org > Subject: Re: [Python-Dev] Yearly PyPI breakage > > > > [cut overlong post] > > Glyph, > > nice sneaky way to try to

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Stefan Krah
> [cut overlong post] Glyph, nice sneaky way to try to divert from the original issue. Your whole post is invalidated by the simple fact that the URL was protected by a hash (which I repeatedly asked to be upgraded to sha256). This was the official scheme promoted by PEP-438, which you should k

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread tritium-list
> > (Is cdecimal substantially different from the _decimal added in 3.5?) > AFAICT, they are unrelated codebases that do about the same thing with the same amount of performance, with the main exception that _decimal in 3.5 does not require one to change their import (or to compile the package

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Terry Reedy
On 5/3/2016 8:56 PM, Glyph wrote: setup.py bdist_wheel' didn't work), and 'twine upload'. `pip install pypi-cdecimal´ should now work and get you an importable `cdecimal´, and if you happen to be lucky enough to run the same OS version I am, you won't even need to build C code. cdecimal users

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Glyph
On May 3, 2016, at 2:38 PM, Stefan Krah wrote: > > But making them completely unreachable does not increase reliability. :) But it does increase security. The other motivation, besides reliability, listed in this section

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Stefan Krah
Łukasz Langa langa.pl> writes: > > I don't fully understand your explanation. Judging by the link that > > Donald posted (thanks!) it seems that PEP 470 introduced extra work > > for him that would not have been present had things been left in place. > > IIRC the PyPI maintainers were constantly

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Łukasz Langa
> On May 3, 2016, at 1:42 PM, Stefan Krah wrote: > > I don't fully understand your explanation. Judging by the link that > Donald posted (thanks!) it seems that PEP 470 introduced extra work > for him that would not have been present had things been left in place. IIRC the PyPI maintainers were

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Stefan Krah
Nathaniel Smith pobox.com> writes: > > If this continues, I'm going to release a premium version that's > > 50% faster and only available from bytereef.org or Anaconda. > > There's no point in making threats -- you're threatening the air. PyPI > is maintained by one overloaded developer (Donald S

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Nathaniel Smith
On Tue, May 3, 2016 at 12:06 PM, Stefan Krah wrote: > > Hello, > > Could someone enlighten me which hoops I have to jump through > this year in order to keep pip downloads working? > > Collecting cdecimal > Could not find a version that satisfies the requirement cdecimal (from > versions: ) > No

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Donald Stufft
> On May 3, 2016, at 3:06 PM, Stefan Krah wrote: > > > Hello, > > Could someone enlighten me which hoops I have to jump through > this year in order to keep pip downloads working? > > This is off topic for python-dev, but https://www.python.org/dev/peps/pep-0470/#i-can-t-host-my-project-o

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Brett Cannon
On Tue, 3 May 2016 at 12:06 Stefan Krah wrote: > > Hello, > > Could someone enlighten me which hoops I have to jump through > this year in order to keep pip downloads working? > > Collecting cdecimal > Could not find a version that satisfies the requirement cdecimal (from > versions: ) > No mat

Re: [Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Łukasz Langa
Why don’t you just *host* the files on PyPI? > On May 3, 2016, at 12:06 PM, Stefan Krah wrote: > > > Hello, > > Could someone enlighten me which hoops I have to jump through > this year in order to keep pip downloads working? > > Collecting cdecimal > Could not find a version that satisfies

[Python-Dev] Yearly PyPI breakage

2016-05-03 Thread Stefan Krah
Hello, Could someone enlighten me which hoops I have to jump through this year in order to keep pip downloads working? Collecting cdecimal Could not find a version that satisfies the requirement cdecimal (from versions: ) No matching distribution found for cdecimal You are using pip version 7.