[issue22757] TclStackFree: incorrect freePtr. Call out of sequence?
New submission from Fay: I have a code that graphs streaming data in a new window. If the cursor is within the graphing window and the cursor has been moved, the graphing window would crash and the message says that "python.exe has stopped working". In the CMD window, the following error is displayed: "TclStackFree: incorrect freePtr. Call out of sequence? This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." I've tried changing from python 2.7.7 to 2.7.8 and matplotlib-1.3.1 to 1.4.2. The problem persists in both cases. -- components: Library (Lib), Tkinter, Windows messages: 230196 nosy: Charleston, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: TclStackFree: incorrect freePtr. Call out of sequence? type: crash versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue22757> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37086] time.sleep error message misleading
New submission from Justin Fay : Using python3.6 and calling `time.sleep` with an invalid argument the `TypeError` raised has the error message "TypeError: an integer is required". This is not the case as a float or integer is acceptable. Using python 2.7 the error message given is better "TypeError: a float is required". -- messages: 343880 nosy: Justin Fay priority: normal severity: normal status: open title: time.sleep error message misleading versions: Python 3.6 ___ Python tracker <https://bugs.python.org/issue37086> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37086] time.sleep error message misleading
Justin Fay added the comment: >From looking at the code for this (note I am not a C programmer so may have >gotten this wrong) _PyTime_FromObject first checks if the object is a float >using PyFloat_Check(obj) this is evident as passing nan to time.sleep raises a >ValueError with the message "Invalid value NaN (not a number)". However if the >object is not a float it next assumes the only valid value to be an integer, >this logic appears fine to me. The problem however is if the object is not an >integer the code raises the error with the message that an integer is >required, it is unaware that a before this branch of the code executes a float >would have been an accepted value. In python I imagine the fix for this would >be along the lines try: float(obj) except (TypeError, ValueError): try: int(obj): except (TypeError, ValueError): raise TypeError('an float or integer is required') -- ___ Python tracker <https://bugs.python.org/issue37086> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com