[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Changes by Terry J. Reedy : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Gabriel Genellina added the comment: Ok, imagine for a moment that your patch is accepted and applied. Python runs in a wide variety of systems. Now imagine that, in a few of them, it stops running. What would you say to defend your changes? "I have no idea why, but it works for me!". I have

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Changes by Luke Kenneth Casson Leighton : Removed file: http://bugs.python.org/file12758/f ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Luke Kenneth Casson Leighton added the comment: here's an updated version, without the cruft. this has a workaround for the problem of stdin being seen as not a tty (!) until _after_ Py_Initialize() is run. Added file: http://bugs.python.org/file12763/x ___

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Luke Kenneth Casson Leighton added the comment: here's another clue: $ ./python.exe stdin_is_interactive: 0 ___ Python tracker ___ ___ Python-

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Luke Kenneth Casson Leighton added the comment: here's a clue: $ ./python.exe -i Python 2.5.2 (r252:60911, Jan 16 2009, 10:34:33) [gcc] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> >>> exit() close failed: [Errno 0] Success $

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Luke Kenneth Casson Leighton added the comment: hi gabriel, thanks for looking at this, and my apologies for not editing the patch to remove debug and other information: i'm in the middle of a comprehensive porting session. WEIRD_DEBUG was me endeavouring to find out what the hell is going on

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

Gabriel Genellina added the comment: what is WEIRD_DEBUG? why do you remove a test from string_tests.py? why do you modify a command in setup.py? What do you mean "the file contents cannot be read under msys+wine"? What specific error you have? The right thing to do would be to analize that

[issue4956] Py_Initialize needs to be done before file load (on msys+wine)

New submission from Luke Kenneth Casson Leighton : this is a _very_ strange case where the file contents cannot be read, under msys+wine, but under _just_ wine (cmd.exe) everything goes absolutely fine. by moving Py_Initialize() to _before_ the file load, it works! -- components: Build