RetroSearch Browse

Mon May 19 17:10:29 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-May/079569.html

On Sat, May 17, 2008 at 5:42 PM, Benjamin Peterson
<musiccomposition at gmail.com> wrote:
> I know Guido has opposed adding Py3k warnings to oct and hex for
> "practical reasons," but I would like to make the case again.
>
> future_buitlins oct and hex will give you the correct Py3k behavior,
> but 2to3 can't convert old hex and oct usage to the new ones. That's
> why is would be helpful to warn about it and encourage people to
> import from future_builtins.

But the difference only matters for people who are parsing the output,
right? I think they'd find out soon enough. I'm still -1.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from https://mail.python.org/pipermail/python-dev/2008-May/079569.html below:

[Python-Dev] oct and hex Py3k warnings