I based my opinion on trying to actually read and understand the output of tknames.py, with your patch done both ways, in a way that I would do in use.  Since class names always begin with upper case, it did not occur to me to read '1' as anything other than 'one'.  '0' is just as easily confused with 'O'.

In both cases, the resemblance depends on the font.  For the Lucida Console I use for IDLE, there is no internal marker dot or bar and O0 only differ slightly in shape.  In a mixed digits and caps string like '' I might have to type the two to be sure which is which.  On the other hand 1l are much more different, as 1 has a rather long horizontal serif while l has none.  Neither comments are true in the fixed font (Courier?) I see now in Firefox.

The semantic clash problem, which is the bigger problem for me, may be stronger for me as a native speaker.  I read '0Frame' and '1Frame' as 'zero Frame' and 'one Frame', not as arbitrary character sequences.  Being able to switch to semantic reading is the point of this issue.