[issue12558] Locale-dependent crash for float width argument to Tkinter widget constructor

2011-07-14 Thread Hans Bering
New submission from Hans Bering hans.ber...@arcor.de: The attached script will crash on a current Ubuntu with Python 3.2 + tcl/tk when using a locale which uses a comma as a decimal separator (e.g., German). It will not crash when using a locale which uses a dot as the decimal separator

[issue12558] Locale-dependent crash for float width argument to Tkinter widget constructor

2011-07-14 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: FYI 'crash' is for segfault. A traceback is just a bug :) I'm not sure that this it is worth having this as a separate bug from #10647, but I'll let someone with tk knowledge decide that. -- nosy: +kbk, r.david.murray,

[issue12558] Locale-dependent crash for float width argument to Tkinter widget constructor

2011-07-14 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +gpolo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12558 ___ ___ Python-bugs-list

[issue12558] Locale-dependent crash for float width argument to Tkinter widget constructor

2011-07-14 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- superseder: scrollbar crash in non-US locale format settings - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12558 ___

[issue12558] Locale-dependent crash for float width argument to Tkinter widget constructor

2011-07-14 Thread Guilherme Polo
Guilherme Polo ggp...@gmail.com added the comment: Why is this a bug ? You passed something that is not supposed to work with tk and tk said so. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12558

[issue12558] Locale-dependent crash for float width argument to Tkinter widget constructor

2011-07-14 Thread Hans Bering
Hans Bering hans.ber...@arcor.de added the comment: Sorry for the misclassification, and thanks for correcting that. I agree, this issue is most likely related to issue 10647; but at some level I think they must be different, because issue 10647 seems to be specific to Python 3.1 under