Neil Tallim <red.hamst...@gmail.com> added the comment: I use the wave module a fair bit and never once encountered this issue, so, yeah, it's probably a pretty low priority for backporting.
It's definitely an edge-case sort of thing, the likes of which anyone affected has already handled in their application-level code. This just makes expected behaviour default behaviour -- if an int is already going in, as would be the case if someone is pre-processing their inputs as a workaround in existing code, it shouldn't change anything. ---------- status: pending -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1512791> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
