Clashing cmp

[Fred L. Drake, Jr.]

François Pinard writes:
 > There is a builtin function named `cmp', but there is also an importable
 > module `cmp' in the standard library.  After a mere `import cmp' (I prefer
 > to avoid `from cmp import SUCH-and-SUCH' if I may), I feel forced to write
 > `__builtins__.cmp' to access the builtin function.
 > 
 > This does not look very elegant to me.  Would not it be better if such
 > elementary clashes were avoided, at least within the standard distribution?

  This tells me nobody has cared about the module until now.  If this
is indeed the case, should it even remain "standard"?  I'd be happy to 
either give it a new name (suggestions?), or call it obsolete.
Removing it is unlikely to break old code.


  -Fred

--
Fred L. Drake, Jr.	     <fdrake at acm.org>
Corporation for National Research Initiatives