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] Restore functions pickling

2016-05-04 Thread Всеволод Величко
Super, since you are not against this feature, I created the issue with the pach[1]. Hopefully you or one of your colleagues will have some time to review it. (I signed the contributor form, changes just not reached the bugtracker yet) [1] http://bugs.python.org/issue26959 2016-05-04 21:55 GMT+0

Re: [Python-Dev] Restore functions pickling

2016-05-04 Thread Brett Cannon
On Wed, 4 May 2016 at 11:39 Всеволод Величко wrote: > Hello, > > I was recently porting my application from Py2 to Py3 and encountered > error, when I accidentally became unable to define my own pickling > mechanism for functions. > Before that I was using it to pickle pure lambdas, registering m

[Python-Dev] Restore functions pickling

2016-05-04 Thread Всеволод Величко
Hello, I was recently porting my application from Py2 to Py3 and encountered error, when I accidentally became unable to define my own pickling mechanism for functions. Before that I was using it to pickle pure lambdas, registering my own handler for cPickle with copy_reg, but after [1] (and relea

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.