[issue12632] Windows GPF with Code Page 65001

STINNER Victor added the comment: > All I'm trying to do is run different versions of Python on the same machine > from the command line. > Some code inside Python now "break" if Python 3.1 is started with Code Page > 65001. Yes, this issue can be seen as a regression introduced in Python 3.

[issue12632] Windows GPF with Code Page 65001

Bruce Ferris added the comment: Victor, thanks for replying and I've had a quick read of everything that went on for issue #1602. I think there's some misunderstanding in what I'm saying here. Maybe this will help clear up what I'm saying... D:\>chcp Active code page: 850 D:\>chcp 65

[issue12632] Windows GPF with Code Page 65001

STINNER Victor added the comment: > Finally, the "fix" you suggest would be applicable if python > used WriteConsole or WriteFile... but it does not! It uses > the write() function, which probably calls WriteConsole > or WriteFile at some point, but does not take unicode characters... The iss

[issue12632] Windows GPF with Code Page 65001

Amaury Forgeot d'Arc added the comment: First, a call to abort() is not a GPF: it's not an interrupt from the kernel or the OS, it's just an explicit (albeit brutal) way to exit from an application. There is no potential back door here. Then, the "Fatal Python error:" line is written to stde

[issue12632] Windows GPF with Code Page 65001

R. David Murray added the comment: If you read what I wrote, I did not say that it wasn't a GPF. I said that an Abort is different from writing into or reading from memory incorrectly (which is what leads to security holes). We don't have many Windows developers active enough to have gotten

[issue12632] Windows GPF with Code Page 65001

Bruce Ferris added the comment: I disagree with the "it's not really a GPF since it calls Abort". Consider the following cmd.exe session... Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. D:\>chcp 65001 Active code page: 65001 D:

[issue12632] Windows GPF with Code Page 65001

STINNER Victor added the comment: > Python shouldn't GPF for ANY reason if it can be easily fixed "Code page 65001" issue cannot be "easily" fixed. Did you read the history of the issue #6058? It took one year and a half to decide that cp65001 cannot be set as an alias to UTF-8. As I wrote,

[issue12632] Windows GPF with Code Page 65001

R. David Murray added the comment: In this case it is not a potential security hole, since in fact the "GPF" comes from Python explicitly calling Abort because of a situation it can't handle, as indicated by the error message from Python. (If it were a true segfault-like error, there would b

[issue12632] Windows GPF with Code Page 65001

Bruce Ferris added the comment: I use code page 65001 because 1) it displays the UTF-8 characters in my text files with "echo " on the command line, and 2) that's Microsoft's "official" (whatever that means) code page for UTF-8, and 3) it works in cmd.exe. Setting aside why I use it, it IS u

[issue12632] Windows GPF with Code Page 65001

STINNER Victor added the comment: You can use PYTHONIOENCODING="utf-8". Code page 65001 is not exactly like Python UTF-8 codec: see issue #6058. Using issue #12281, it may be possible to implement a cp65001 codec. See also issue #1602 for the Windows console. Why do you use cp65001? ---

[issue12632] Windows GPF with Code Page 65001

Changes by Ezio Melotti : -- nosy: +ezio.melotti, haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue12632] Windows GPF with Code Page 65001

Changes by Bruce Ferris : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue12632] Windows GPF with Code Page 65001

New submission from Bruce Ferris : The following scenario GPFs on Windows Vista using cmd.exe... D:\>python Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> ^Z D:\>chcp 6