[issue2734] 2to3 converts long(itude) argument to int

2010-07-23 Thread Peter
Changes by Peter : -- nosy: +maubp ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailma

[issue2734] 2to3 converts long(itude) argument to int

2010-07-22 Thread Eric Talevich
Eric Talevich added the comment: This issue still occurs when the name "long" is a function argument: def double(long): return long * 2 2to3 converts it to: def double(long): return int * 2 Should I file a new bug, or can someone reopen this? -- nosy: +eric-talevich versio

[issue2734] 2to3 converts long(itude) argument to int

2008-12-31 Thread Benjamin Peterson
Benjamin Peterson added the comment: I hope r68106 helps. 2to3 now refuses to change long if it is being assigned to, the name of a function or class, the name of an argument, or an attribute. -- resolution: -> fixed status: open -> closed ___ Pytho

[issue2734] 2to3 converts long(itude) argument to int

2008-12-10 Thread Benjamin Peterson
Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: collinwinter -> benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2734] 2to3 converts long(itude) argument to int

2008-12-10 Thread Robin Stocker
Changes by Robin Stocker <[EMAIL PROTECTED]>: -- nosy: +robin.stocker ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue2734] 2to3 converts long(itude) argument to int

2008-12-10 Thread Reto Schüttel
Reto Schüttel <[EMAIL PROTECTED]> added the comment: This is even worse in case of attributes (like in pyephem for the observer object): class Foo(object): def __init__(self): self.long = 1 x = Foo() print x.long 2to3 produces: --- attr.py (original) +++ att

[issue2734] 2to3 converts long(itude) argument to int

2008-12-08 Thread Armin Ronacher
Armin Ronacher <[EMAIL PROTECTED]> added the comment: This could probably be fixed by adding a `is_builtin` helper function to the fixer_util module that checks if the name is not overriden in the module. I would use something like a weak dictionary for the `find_binding` function because that c

[issue2734] 2to3 converts long(itude) argument to int

2008-05-16 Thread Georg Brandl
Georg Brandl <[EMAIL PROTECTED]> added the comment: Let me note that this also happens for assignments like: long = Type("long", "l") -- nosy: +georg.brandl __ Tracker <[EMAIL PROTECTED]> ___

[issue2734] 2to3 converts long(itude) argument to int

2008-05-01 Thread Collin Winter
Collin Winter <[EMAIL PROTECTED]> added the comment: It *could* be implemented for all fixers, but since it's fairly expensive, I'd rather limit it to cases where the problem is more likely to occur (for example, unicode -> str doesn't meet this threshold IMHO). _

[issue2734] 2to3 converts long(itude) argument to int

2008-05-01 Thread Benjamin Peterson
Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This seems to happen whenever argument are types that need to be renamed (eg. unicode -> str) Can this be fixed globally? -- nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]>

[issue2734] 2to3 converts long(itude) argument to int

2008-05-01 Thread Collin Winter
Collin Winter <[EMAIL PROTECTED]> added the comment: Agreed. There's code in fix_next to detect this kind of case. I'll see what I can do about generalizing it to support fix_long. __ Tracker <[EMAIL PROTECTED]> _

[issue2734] 2to3 converts long(itude) argument to int

2008-05-01 Thread Charles McCreary
New submission from Charles McCreary <[EMAIL PROTECTED]>: The 2to3 converter converts variables named "long" to "int". Original: long is an argument (longitude) def add_test_qtrmin(tdb, lat, long, area_id, call_center=""): Converted: def add_test_qtrmin(tdb, lat, int, area_id, call_center=""):