=< currently displays with the ≤ glyph. I would expect this for <=, but for =< I would prefer this to display as the two separate glyphs =< with no ligature. I suspect many other Python programmers feel the same way, since the characters =< frequently appear in __repr__ strings that have nothing to do with <= comparison, e.g.:
>>> from collections import namedtuple
>>> Foo = namedtuple('Foo', 'bar')
>>> Foo(bar=object())
Foo(bar=<object object at 0x1071b7ef0>)The current behavior results in Foo(bar≤object object at 0x107...>) being shown, which is actually misleading.
I'm guessing Python isn't the only context where the =< substring means something very different from <=.
Would you consider removing the =< → ≤ ligature?
Thanks for your consideration and for sharing this wonderful font! <333
=<currently displays with the≤glyph. I would expect this for<=, but for=<I would prefer this to display as the two separate glyphs=<with no ligature. I suspect many other Python programmers feel the same way, since the characters=<frequently appear in__repr__strings that have nothing to do with<=comparison, e.g.:The current behavior results in
Foo(bar≤object object at 0x107...>)being shown, which is actually misleading.I'm guessing Python isn't the only context where the
=<substring means something very different from<=.Would you consider removing the
=< → ≤ligature?Thanks for your consideration and for sharing this wonderful font! <333