[issue29819] Avoid raising OverflowError in truncate() if possible

2019-05-27 Thread Joannah Nanjekye
Change by Joannah Nanjekye : -- nosy: +nanjekyejoannah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue29819] Avoid raising OverflowError in truncate() if possible

2017-03-19 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Issue29852 is not strict dependency, but it may make the solution of this issue simpler. -- dependencies: +Argument Clinic: add common converter to Py_ssize_t that accepts None ___ Python tracker

[issue29819] Avoid raising OverflowError in truncate() if possible

2017-03-15 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue29819] Avoid raising OverflowError in truncate() if possible

2017-03-15 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- nosy: +Oren Milman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue29819] Avoid raising OverflowError in truncate() if possible

2017-03-15 Thread Serhiy Storchaka
New submission from Serhiy Storchaka: os.truncate(), os.ftruncate() and truncate() methods of file-like objects raise OverflowError when the argument is out of ranger of certain C type. It would be better to extend the behavior of small integers to large integers. ValueError is raised for nega