[Python-mode] Poll - Fwd: [Bug 858304] [NEW] variable name is highighted on LHS of equality (==) test, but shouldn't be

[Georg Brandl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Andreas,

if anything is highlighted, then it should be only locals at assignment.
Highlighting other assignments gets much too messy on the eyes (and if you
start highlighting "variable" (no such thing in Python anyway) names
on access too, you will have to color most of the code...

Georg

Am 25.09.2011 18:47, schrieb Andreas Röhler:
> Hi folks,
> 
> possibility of highlighting variable name is a new feature in the trunk.
> 
> It's not clear however, in which circumstances variable should get 
> highlighted -if at all.
> 
> Also might drop that, should it not be considered useful.
> 
> Would be nice to get some comments before a release.
> 
> Thanks,
> 
> Andreas
> 
> 
> 
> -------- Original-Nachricht -------- Betreff: [Bug 858304] [NEW] variable
> name is highighted on LHS of equality	(==) test, but shouldn't be Datum:
> Sat, 24 Sep 2011 15:58:38 -0000 Von: Andrew Uzilov
> <858304 at bugs.launchpad.net> Antwort an: Bug 858304
> <858304 at bugs.launchpad.net> An: andreas.roehler at online.de
> 
> Public bug reported:
> 
> This pertains to the lp:python-mode branch, I think this bug does not occur
> in 6.0.2.
> 
> LHS of equality (==) tests now gets highlighted, but it shouldn't.  The 
> highlighting should only be for LHS on assignment (=) expressions.  For 
> example:
> 
> if someVar == 5: doSomething()
> 
> "someVar" is highlighted.  However, if you wrap it with something, like 
> this:
> 
> if len (someVar) == 5: doSomething()
> 
> "someVar" is not highlighted.
> 
> ** Affects: python-mode Importance: Undecided Status: New
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk5/XdIACgkQN9GcIYhpnLCYxQCcDzhM2l8NPm9ZgQMFlYCcbFHG
hm0AnRDSZfEX8wEpEjjFVq1V2U2LyqXq
=tTNq
-----END PGP SIGNATURE-----