RetroSearch Browse

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

Showing content from http://mail.python.org/pipermail/python-dev/attachments/20091011/7fd84f19/attachment.htm below:

<br><br><div class="gmail_quote">On Sun, Oct 11, 2009 at 13:00, Glyph Lefkowitz <span dir="ltr"><<a href="mailto:glyph@twistedmatrix.com">glyph@twistedmatrix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class="im">On Sun, Oct 11, 2009 at 3:48 PM, Guido van Rossum <span dir="ltr"><<a href="mailto:guido@python.org" target="_blank">guido@python.org</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">

I'm -0 -- mostly because of the 3rd party doctests and perhaps also<br>
because I'd like 3.x to have some carrots. (I've heard from at least<br>
one author who is very happy with 3.x for the next edition of his<br>
"programming for beginners" book.)<br></blockquote></div><div><br>This reasoning definitely makes sense to me; with all the dependency-migration issues 3.x could definitely use some carrots.Â However, I don't think I agree with it, because this doesn't feel like a big new feature, just some behavior which has changed.Â The carrots I'm interested in as a user are new possibilties, like new standard library features, a better debugger/profiler, or everybody's favorate bugaboo, multicore parallelism.Â (Although, to be fair, the removal of old-style classes qualifies.)<br>

<br></div></div></blockquote><div><br></div><div>Sure, but if people like Mark are having to spend their time backporting every bit of behaviour like this then we won't have the time and energy to add the bigger carrots to 3.x to help entice people to switch.</div>

<div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div>I'd much rather have my doctests and float-repr'ing code break on 2.7 so I can deal with it as part of a minor-version upgrade than have it break on 3.x and have to deal with this at the same time as the unicode->str explosion.Â It feels like a backport of this behavior would make the 2->3 transition itself a little easier.</div>

</div></blockquote><div><br></div><div>Maybe, but as Mark pointed out, at least in the test suite for Python, there was no breakage. This will only be an issues if someone does::</div><div><br></div><div>Â Â >>> x</div>

<div>Â Â 0.029999999</div><div><br></div><div>instead of::</div><div><br></div><div>Â Â >>> x == 0.03</div><div>Â Â True</div><div><br></div><div>Plus it should be obvious when a doctest breaks with 0.03 != 0.0299999999999 what has happened.</div>

<div><br></div><div>I'm with Guido: -0 on the backport, especially with Mark feeling neutral on wanting to put the effort in.</div><div><br></div><div>-Brett</div></div>

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4