RetroSearch Browse

Sun Dec 17 10:46:45 EST 2017 · https://mail.python.org/pipermail/python-dev/2017-December/151338.html

My gut suggests me not to do this (neither here nor in other similar
cases). I doubt there's much of a performance benefit anyway.

On Sat, Dec 16, 2017 at 10:04 PM, 尚辉 <shangdahao at gmail.com> wrote:

> Hi, guys
>
> In https://github.com/python/cpython/pull/4904, I made csv.DictReader
> returning regular dict instead of OrderedDict. But this code could break
> existing code that relied on methods like move_to_end() which are present
> in OrderedDict() but not in dict().
>
> As rhettinger suggested, such code is either unlikely or rare, so it would
> be net less disruptive for users to just go forward with this patch.
>
> So, would we just go forward with this patch or having a deprecation
> period before this patch?
>
> Any help is big thanks.
>
> --
>
>
> Best Regards .
>
> shangdahao
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> guido%40python.org
>
>

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171217/467bdac3/attachment.html>

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

Showing content from https://mail.python.org/pipermail/python-dev/2017-December/151338.html below:

[Python-Dev] Decision of having a deprecation period or not for changing csv.DictReader returning type.