[issue2805] 2to3 doesn't correct divisions

Benjamin Peterson added the comment: I concur with Raymond. There isn't yet a "-3" warning for class division, though. I suppose the compiler could emit one when "/" is used without from __future__ import division. That's another issue, though. -- resolution: -> rejected status: open -

[issue2805] 2to3 doesn't correct divisions

Raymond Hettinger added the comment: I thought the right way to handle this is with a -3 option. That's the only way to reliably detect the intended meaning of / and its change in meaning in 3.0. -- nosy: +rhettinger ___ Python tracker

[issue2805] 2to3 doesn't correct divisions

Changes by Daniel Diniz : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue2805] 2to3 doesn't correct divisions

Changes by Armin Ronacher <[EMAIL PROTECTED]>: -- nosy: +aronacher ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list maili

[issue2805] 2to3 doesn't correct divisions

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: +1 for going ahead and writing a fixer. -- nosy: +rbp __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2805] 2to3 doesn't correct divisions

Collin Winter <[EMAIL PROTECTED]> added the comment: I say do it before the GSoC projects complete. Those projects will take months, and we can't stop development for that long. __ Tracker <[EMAIL PROTECTED]>

[issue2805] 2to3 doesn't correct divisions

Guilherme Polo <[EMAIL PROTECTED]> added the comment: If I were to add such fixer, should I wait for changes coming by gsoc projects ? I did a quick pass through 2to3 code a while ago, but I'm very far from understanding it in a good manner so I'm not sure if I should starting doing that now beca

[issue2805] 2to3 doesn't correct divisions

Collin Winter <[EMAIL PROTECTED]> added the comment: My gut feeling is that the number of cases where both operands are written as literals is exceedingly small when compared to the number of cases where one or both is an identifier. Since 2to3 doesn't support type inference, we'd miss the releva

[issue2805] 2to3 doesn't correct divisions

New submission from Guilherme Polo <[EMAIL PROTECTED]>: Given the sample code: for i in range(len([1, 2]) / 2): pass print 2 / 3 2to3 tells no files need to be modified after running it over this code, but range doesn't accept float values and the print result will differ. Would it be too