Guy Taylor <thebigguy.co...@gmail.com> added the comment: What ever change is made to the new CPythons the old docs should be updated to prevent confusion, with truncate([size]).
On fixing it for the future I would agree that supporting it as a keyword argument is preferred, as it is more pythonic (in my opinion). However this would cause ether backwards incompatibility or ambiguity in the language (ie. truncate(0, size=1) or need the deprecate, warn then removal stages taken three release cycles). Maybe the less perfect but acceptable solution is just to change the docs and wait for Python 4k for the real fix....? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14586> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
