> > The performance error for strings should be considered an anomaly, not a > feature to be extended to anything that could be used, or misused, with > non-linear behaviour.
I’m pretty sure that using sum with strings was a real issue in real code before it was disallowed. But the irony is that strings in the cPython interpreter have an optimization that makes it actually work fine :-( I’d rather remove the error for strings than add more Type limitations. -CHB At the very least, we would probably need to see > evidence that this issue (poor performance) is a widespread problem > before breaking code which works fine for small N. > > > -- > Steve > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/FSD5TENDE4RLESDRPWN7WJ3WJMFPRASC/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- Christopher Barker, PhD (Chris) Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/7YRS7I7XOIFP47HKWOGVG3X2IW5F4HYG/ Code of Conduct: http://python.org/psf/codeofconduct/
