-
-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OS X: python3 from python-3.1.dmg crashes at startup #50642
Comments
There was a report[1] on c.l.p. that python3 from the OS X Python 3.1 newton:~ dickinsm$ LANG=utf-8 python3 The core dump isn't useful: just lots of 'No symbol table info This is on OS X 10.5.7/Intel. I can't reproduce it with either the py3k branch or the release31-maint I suspect that this has to do with the behaviour of nl_langinfo(CODESET) Ronald, any ideas? [1] http://mail.python.org/pipermail/python-list/2009-June/718255.html |
This is a side effect of the fix for bpo-6202. Prior to r73268, |
Note, you can produce the same error on OS X or linux by setting That raises the question of how far python should go in protecting the |
"... create_stdio passes PYTHONIOENCODING ..." |
While googling for the source of this problem, I found other software I just wish I understood *why* nl_langinfo(CODESET) is returning "" in It seems that a lot of people end up with an OS X Terminal setup such that |
The manpage says that nl_langinfo returns an empty string when there is There is validity in saying that 'LANG=utf-8' is an invalid setting, the I wouldn't mind falling back to utf-8 as the default codeset when I do wonder how the user ended up with LANG=utf-8 in the first place. |
Agreed. But that doesn't really explain why e.g. LANG=en_US also
Me too. As far as I can gather, it's a result of setting the Terminal |
The attached patch (bpo-6393-fix.patch) seems to fix the issue. Could you please test and have a look at the patch? It basicly tests if I intent to apply this patch unless someone objects to that. |
Thanks, Ronald! The patch fixes the problem for me. The patch doesn't look quite right, though: in the else clause, On the subject of Terminal and LANG, LC_CTYPE settings, I found an http://pastie.textmate.org/111807 Indeed, after setting my region to 'South Africa' in Preferences -> newton:~ dickinsm$ locale And then python3 crashes on startup as above. This is on a newborn (3- |
Good catch, the code in the else is indeed in the wrong order. |
Looks good and the "patched" patch also works in a py3k installer build. BTW, Mark, I was curious as to why you were unable to reproduce the |
Once this patch is checked in, should we do an emergency 3.1.1 release? |
I'm don't know whether this is really worth a 3.1.1, all by itself. |
I see this problem on both MacOS X 10.5 and on Windows. This is when using On MacOS X the error is: Fatal Python error: Py_Initialize: can't initialize sys standard streams On Windows the error is: Fatal Python error: Py_Initialize: can't initialize sys standard streams The talk about the fix mentioned it only addressing MacOS X. What about |
Hmmm, actually my MacOS X error is different, although Windows one is |
You can ignore my MacOS X example as that was caused by something else. My question still stands as to whether the fix will address the similar |
I have created bpo-6501 for my Windows variant of this problem given that Seeing that the fix for the MacOS X issue is in Python code, I will when I |
I've applied the fixed version of my patch in r74687 (3.x) and r74688 |
There is an error in r74687 (3.x) and r74688 (3.1) fixes - in the 'else' |
The missing return result in the else case has been subsequently fixed in |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: