Benjamin Peterson <benja...@python.org> added the comment: I'm rejecting this patch again not because I think it's any worse than the status quo (I think they're about equally incorrect/correct), but because this is now released behavior and changing it may result in backwards incompatibility. Also, people can easily remove this ambiguity in a 2.x compatible fashion by explicitly listing the types (str,) or (str, unicode) instead of using the types module.
---------- status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5425> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
