RetroSearch Browse

Fri Jul 11 02:31:09 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-July/135454.html

On 07/10/2014 04:57 PM, Alexander Belopolsky wrote:
> On Thu, Jul 10, 2014 at 2:59 PM, Mark Lawrence wrote:
>>
>> I'm just curious as to why there are 54 open issues after both of
>> these PEPs have been accepted and 384 is listed as finished.  Did
>>  we hit some unforeseen technical problem which stalled development?
>
> I tried to bring some sanity to that effort by opening a "meta issue":
>
> http://bugs.python.org/issue15787
>
> My enthusiasm, however, vanished after I reviewed the refactoring for the datetime module:
>
> http://bugs.python.org/issue15390
>
> My main objections are to following PEP 384 <http://www.python.org/dev/peps/pep-0384/> (Stable ABI) within stdlib
> modules.  I see little benefit for the stdlib (which is shipped fresh with every new version of Python) from following
> those guidelines.

If we aren't going to implement the changes (and I agree there's little value for the stdlib to do so), let's mark the 
issues as "won't fix" and close them.

And thanks, Mark, for bringing it up.

--
~Ethan~

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-July/135454.html below:

[Python-Dev] PEP 3121, 384 Refactoring Issues