[issue417388] pythonw.exe will not work

Change by admin : -- github: None -> 34374 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400764] fix to make os.popen work under pythonw.exe

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400764] fix to make os.popen work under pythonw.exe

Change by admin : -- github: None -> 32534 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Steve Dower added the comment: Assuming the fix for this was released, given lack of other information. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Steve Dower added the comment: > FWIW, the very first thing that I checked was the dependencies of pythonw.exe The version in the Store has a different build of pythonw.exe (because it has to be able to determine its user site-packages location differently). Dump of file C:\Program Fi

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Terry J. Reedy added the comment: For me, 'pyw -3.7 -m idlelib' in Command Prompt opens IDLE with 3.7.5. So does the equivalent run by clicking the IDLE icon: C:\Programs\Python37\pythonw.exe "C:\Programs\Python37\Lib\idlelib\idle.pyw" This report reminds me that I shoul

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Eryk Sun added the comment: > At least one package in 3.8 still contained a dependency on the C++ > runtime FWIW, the very first thing that I checked was the dependencies of pythonw.exe, in case maybe I had a dependent DLL that's not distributed with Windows. There's nothi

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Jon added the comment: When I have some time. Maybe this weekend. 3.7.4 is working ok right now for production level. So I didn't bother with anything else yet. Might help someone else in the meantime though. Glad to see that someone is taking the complaint seriously :) --

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Steve Dower added the comment: Can you try installing https://aka.ms/vs/16/release/VC_redist.x64.exe and then see if it makes a difference? At least one package in 3.8 still contained a dependency on the C++ runtime, which we do not include, and it's possible that 3.7.5 had the same issue.

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Jon added the comment: BTW, I have win10 x64 v 1809 b 17763.720. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Jon added the comment: @eryk. Could I just have separate folder with each python minor version? I would keep it portable and just reference the python/pythonw.exe filepath directly for each version when I run. I could just download the 3.7.5 and drop it anywhere

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Eryk Sun added the comment: > Let me know if you are unable to reproduce it. x64 pythonw.exe and pyw.exe (3.7.5, 2019-10-14) work for me in Windows 10.0.18362. I have them installed for all users, respectively in "C:\Program Files\Python37" and "C:\Windows". Try

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

for pythonW.exe python/pw.exe works fine for both 3.7.4 and 3.7.5 (x86 and x64 versions) pythonW/pyW.exe works fine for 3.7.4 but not 3.7.5 (x86 and x64 versions) This is the first time i've ever had this issue. python 3.6.x. I originally thought it was a win10 issue because I am setting up a new

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Paul Moore added the comment: Can you give an example of a script that fails? If you try to print (or otherwise use the standard IO streams) pythonw will fail, because there are no stdio streams for a GUI executable - and the traceback, which goes to stderr by default, will be lost. This

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

Change by Jon : -- title: v3.7.5 py script run ok with python.exe but not pythonw.exe (python console not working) -> v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working) ___ Python tracker <

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python console not working)

Change by Jon : -- title: v3.7.5 py script run ok with python.exe but not pythonw.exe (python console) -> v3.7.5 py script run ok with python.exe but not pythonw.exe (python console not working) ___ Python tracker <https://bugs.pyth

[issue38533] v3.7.5 py script run ok with python.exe but not pythonw.exe (python console)

Jon added the comment: I installed v3.7.4 x86 and scripts work with `pythonw.exe` and `pyw.exe` I also tested v3.7.4 x64 bit and scripts also work ok. So that is some good news. This proves that pythonw (python console) for 3.7.5 is not working for some unknown reasons. It is not related

[issue38533] py script runs with python.exe but not pythonw.exe (python console)

Jon added the comment: by the way, just to be sure, I am actually running the python.exe / py.exe / pythonw.exe / pyw.exe from the full file path just to be sure. e.g. %LOCALAPPDATA%\Programs\Python\Launcher\pyw.exe test.py -- ___ Python

[issue38533] py script runs with python.exe but not pythonw.exe (python console)

New submission from Jon : 3.7.5. Any py script that I run with python.exe or py.exe executes just fine. But if I try to run any py script with pythonW.exe or pyW.exe it will not run. I don't know where the logging for the python executable is located. On the same machine, java.exe

[issue13582] IDLE and pythonw.exe stderr problem

Terry J. Reedy added the comment: Good question. There are two issues when starting IDLE with pythonw.exe, so that sys.__stderr__ and sys.stderr are initially None. 1. None.write is an attribute error that crashes Python. Therefore, don't do that. Instead use print. By default, and when

[issue13582] IDLE and pythonw.exe stderr problem

anthony shaw added the comment: Revisiting this issue as it's still open. The original patch was for 3.3a0, there have been many changes to both IDLE and the Windows build since, including the recent IDLE entry point in the new Windows installer. Steve, Terry, please could you review to

Re: pythonw.exe error

On Monday, October 30, 2017 at 10:11:49 PM UTC+5:30, Igor Korot wrote: > Hi, > > > > On Oct 30, 2017 11:27 AM, "George Kalamaras via Python-list" wrote: > > When I am running IDLE return to me Missing python36.dll error > > Στάλθηκε από την Αλληλογραφία για Windows 10 > > > Could you please

Re: pythonw.exe error

Hi, On Oct 30, 2017 11:27 AM, "George Kalamaras via Python-list" < python-list@python.org> wrote: When I am running IDLE return to me Missing python36.dll error Στάλθηκε από την Αλληλογραφία για Windows 10 Could you please translate this from Greek? Thank you. --

pythonw.exe error

When I am running IDLE return to me Missing python36.dll error Στάλθηκε από την Αλληλογραφία για Windows 10 -- https://mail.python.org/mailman/listinfo/python-list

[issue13582] IDLE and pythonw.exe stderr problem

Changes by Terry J. Reedy : -- assignee: -> terry.reedy stage: test needed -> patch review versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.3, Python 3.4 ___ Python tracker

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

Changes by Serhiy Storchaka storch...@gmail.com: -- resolution: - not a bug status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

Changes by Serhiy Storchaka storch...@gmail.com: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___ ___

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

New submission from Edward K. Ream: In Python3.2 xml.sax.saxutils.XMLGenerator.__init__ succeeds if the out keyword argument is not given and sys.stdout is None, which will typically be the case when using pythonw.exe. Alas, on Python3.4, the ctor throws an exception in this case

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

Serhiy Storchaka added the comment: In any case XMLGenerator is not usable if the out keyword argument is not given and sys.stdout is None. Just the exception will be raised later. I consider early failure as a feature, not a bug. -- nosy: +serhiy.storchaka

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

R. David Murray added the comment: Agreed. I was going to ask what it was that 3.2 did that was useful. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___

[issue22819] Python3.4: xml.sax.saxutils.XMLGenerator.__init__ fails with pythonw.exe

Serhiy Storchaka added the comment: FYI the code was changed in issue1470548. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22819 ___ ___

[issue22730] ensurepip should work with pythonw.exe

New submission from Steve Dower: I'd like to be able to run ensurepip in the 3.5 installer with pythonw.exe, to avoid having the console window appear. Unfortunately, pip requires a valid value for sys.__stdout__. This patch adds a dummy value for __stdout__ that allows pip to be installed

[issue22730] ensurepip should work with pythonw.exe

Donald Stufft added the comment: This looks OK to me. I'm not a Windows person are there changes in pip that would make sense to make it work without this patch? -- nosy: +Marcus.Smith, pmoore ___ Python tracker rep...@bugs.python.org

[issue22730] ensurepip should work with pythonw.exe

Steve Dower added the comment: I think the only thing pip could do is to stop using print(), which is not a reasonable request. It may be reasonable to change pythonw to use dummy IO streams by default, but that may cause programs to print() messages expecting the user to see them. It's also

[issue22730] ensurepip should work with pythonw.exe

Donald Stufft added the comment: The development version of pip switches things over to using the Python logging framework instead of a homegrown one which more or less relies on print(). Probably we could detect if we don't have a stdout and just not output anything? People can pass a

[issue22730] ensurepip should work with pythonw.exe

Steve Dower added the comment: That change sounds like it'll be enough, and I'd be surprised if the logging module doesn't already handle the case with no streams. (Aside: it'd be nice for ensurepip to have a log file parameter that can be passed through.) I'll hold off on merging this in

[issue22730] ensurepip should work with pythonw.exe

Paul Moore added the comment: This looks reasonable to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22730 ___ ___ Python-bugs-list mailing

[issue22730] ensurepip should work with pythonw.exe

Paul Moore added the comment: Wait, sorry I misread the discussion (long day here). If we can do this in pip yes that would be better. It looks like we can detect when we're being run via pythonw by checking if sys.stdout is None. -- ___ Python

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Serhiy Storchaka added the comment: Error messages are already silenced if sys.stderr is None or closed. sys.stderr.close() 1/0 sys.stderr = None 1/0 I think that such things as _Errbox are application level solutions. report_callback_exception() is designed to be overwritten for

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Terry J. Reedy added the comment: Since traceback.print_exception already uses print statememts, your patch *is* sufficient to trap the remaining stderr exception. Go ahead. The doctring for report_callback_exception calls it an 'internal function'. To me, that implies 'ignore this' rather

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Terry J. Reedy added the comment: And yes, I am thinking about a broader fix for Idle -- replacing stderr None with something writable. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22384

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Roundup Robot added the comment: New changeset 994a16b51544 by Serhiy Storchaka in branch '2.7': Issue #22384: An exception in Tkinter callback no longer crashes the program https://hg.python.org/cpython/rev/994a16b51544 New changeset c62fad86fac3 by Serhiy Storchaka in branch '3.4': Issue

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Serhiy Storchaka added the comment: Thank you for suggested docstring Terry. There is related question on StackOverflow: http://stackoverflow.com/questions/4770993/silent-exceptions-in-python-tkinter-should-i-make-them-louder-how -- ___ Python

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Serhiy Storchaka added the comment: Thank you Aivar for helpful report. -- resolution: - fixed stage: patch review - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22384

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Changes by Serhiy Storchaka storch...@gmail.com: -- keywords: +needs review nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22384 ___

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Terry J. Reedy added the comment: In a pythonw process, stdout and stderr are initially None unless and until changed. (This is something we need to do for the Idle process itself.) Writing to None generates an AttributeError. Uncaught exceptions stop the Python process. The patch works,

Re: pythonw.exe has stopped working

Title] pythonw.exe [Main Instruction] pythonw.exe has stopped working [Content] A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. [Close program] It's strange that while it's able

Re: pythonw.exe has stopped working

. I know it might work if I split my test case but have any of you encountered this problem and knows how to fix it ? some fix like providing more memory or specifying some parameter when pythonw.exe starts? Install more memory? It might help if you show us the code that crashes. -- Steven

Re: pythonw.exe has stopped working

Steven D'Aprano steve+comp.lang.pyt...@pearwood.info: rahuldbha...@gmail.com wrote: encountered this problem and knows how to fix it ? some fix like providing more memory or specifying some parameter when pythonw.exe starts? Install more memory? It might help if you show us the code

Re: pythonw.exe has stopped working

On 9/12/2014 1:48 AM, rahuldbha...@gmail.com wrote: Hello Folks, I'm using RIDE -- Robot Framework Test Data Editor RIDE 1.3 running on Python 2.7.6. When I click on some of my test case the RIDE GUI hangs and gives bellow error message. Run RIDE with python, not pythonw, from a command

pythonw.exe has stopped working

Hello Folks, I'm using RIDE -- Robot Framework Test Data Editor RIDE 1.3 running on Python 2.7.6. When I click on some of my test case the RIDE GUI hangs and gives bellow error message. [Window Title] pythonw.exe [Main Instruction] pythonw.exe has stopped working [Content] A problem

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Serhiy Storchaka added the comment: May be this patch would help. -- assignee: - serhiy.storchaka keywords: +patch nosy: +serhiy.storchaka stage: - patch review type: crash - behavior versions: +Python 2.7, Python 3.5 Added file:

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

New submission from Aivar Annamaa: Seems that the statement 'sys.stderr.write(Exception in Tkinter callback\n)' in Tk.report_callback_exception fails when the program is run with pythonw.exe, and brings down the whole process. A simple sample is attached. -- files: demo.py messages

[issue22384] Tk.report_callback_exception kills process when run with pythonw.exe

Changes by Aivar Annamaa aivar.anna...@gmail.com: -- components: +Tkinter type: - crash versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22384 ___

Re: How to tell Script to use pythonw.exe ?

On Tuesday, July 2, 2013 9:20:12 PM UTC-4, goldtech wrote: Hi, I want to run a .py file script using pythonw.exe so the DOS box will not open. Is there a way from inside the script to say run me with pythonw.exe and not python.exe? Thanks -- https://mail.python.org/mailman

[issue13582] IDLE and pythonw.exe stderr problem

Terry J. Reedy added the comment: Idle start up seems unnecessarily fragmented into multiple files. idlelib/__main__.py idlelib/idle.py idlelib/idlew.py can all be started from the command line by name with either python or pythonw or run once by import. idlelib/__main__.py can also be

[issue13582] IDLE and pythonw.exe stderr problem

Todd Rovito added the comment: Terry, Bottom line I can't seem to get this patch to do anything for me. Before the patch is applied IDLE seems to be handling warnings and exceptions just fine in PyShell on the Mac. I get no crash and the output matches the normal console. Here is a

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On Wed, 3 Jul 2013, Dennis Lee Bieber wrote: Consider that the Powershell default is to /prevent/ execution of script files unless some security settings have been changed; even local script files need to be signed to be executed. Protip: No they don't - wrap it in a cmd/bat file and

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 2013.07.04 09:08, Wayne Werner wrote: powershell -ExecutionPolicy Bypass -File ... \o/ Microsoft security at it again! (reminds me a bit of just pushing Cancel to log into windows 98, I think it was) From an MSDN page linked in one of the answers: Now, why is PowerShell.exe

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On Fri, Jul 5, 2013 at 8:12 AM, Andrew Berg robotsondr...@gmail.com wrote: On 2013.07.04 09:08, Wayne Werner wrote: powershell -ExecutionPolicy Bypass -File ... \o/ Microsoft security at it again! (reminds me a bit of just pushing Cancel to log into windows 98, I think it was) From an

DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 03/07/2013 02:34, Andrew Berg wrote: DOS is long dead, and is much, much different under the hood from the console subsystem in modern versions of Windows. While this is clearly true, it's by no means unusual for people to refer to the DOS Box or talk about DOS commands etc. even when

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On Wed, Jul 3, 2013 at 5:34 PM, Tim Golden m...@timgolden.me.uk wrote: On 03/07/2013 02:34, Andrew Berg wrote: DOS is long dead, and is much, much different under the hood from the console subsystem in modern versions of Windows. While this is clearly true, it's by no means unusual for

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 2013.07.03 02:34, Tim Golden wrote: While this is clearly true, it's by no means unusual for people to refer to the DOS Box or talk about DOS commands etc. even when they're quite well aware of the history of Windows and its Console subsystem. It's just quicker than saying Console Window or

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 03/07/2013 09:28, Andrew Berg wrote: On 2013.07.03 02:34, Tim Golden wrote: While this is clearly true, it's by no means unusual for people to refer to the DOS Box or talk about DOS commands etc. even when they're quite well aware of the history of Windows and its Console subsystem. It's

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 2013-07-03 09:51, Tim Golden wrote: We can certainly agree on this. I can't count the number of emails I've deleted as too hot-headed in response to dismissive comments about Windows as a platform. Some of them, at least, appear to be from people who last actually used Windows back in the

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 03/07/2013 13:50, Tim Chase wrote: On 2013-07-03 09:51, Tim Golden wrote: We can certainly agree on this. I can't count the number of emails I've deleted as too hot-headed in response to dismissive comments about Windows as a platform. Some of them, at least, appear to be from people who

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On Wed, 03 Jul 2013 14:00:49 +0100, Tim Golden wrote: Goodness, I doubt if you'll find anyone who can seriously make a case that the Windows command prompt is all it might be. I'm not a Powershell user myself but people speak highly of it. I understand that Powershell is aimed more for batch

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On 2013-07-03 13:19:26 +, Steven D'Aprano said: On Wed, 03 Jul 2013 14:00:49 +0100, Tim Golden wrote: Goodness, I doubt if you'll find anyone who can seriously make a case that the Windows command prompt is all it might be. I'm not a Powershell user myself but people speak highly of it.

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On Wed, Jul 3, 2013 at 10:50 PM, Tim Chase python.l...@tim.thechases.com wrote: On 2013-07-03 09:51, Tim Golden wrote: We can certainly agree on this. I can't count the number of emails I've deleted as too hot-headed in response to dismissive comments about Windows as a platform. Some of them,

Re: How to tell Script to use pythonw.exe ?

Στις 3/7/2013 6:43 πμ, ο/η Tim Roberts έγραψε: goldtech leeg...@operamail.com wrote: I just changed the file extension of the script file from .py to .pyw and it uses pythonw.exe. I didn't read it anywhere, just intuited it and tried it. Python has some very smart people working the language

Re: How to tell Script to use pythonw.exe ?

On Jul 3, 2013 8:27 AM, Νίκος ni...@superhost.gr wrote: Στις 3/7/2013 6:43 πμ, ο/η Tim Roberts έγραψε: goldtech leeg...@operamail.com wrote: I just changed the file extension of the script file from .py to .pyw and it uses pythonw.exe. I didn't read it anywhere, just intuited it and tried

Re: How to tell Script to use pythonw.exe ?

of the script file from .py to .pyw and it uses pythonw.exe. I didn't read it anywhere, just intuited it and tried it. Python has some very smart people working the language... While your statement is true, that's not what happened here. Windows has long had the ability to associate

Re: DOS or not? [was Re: How to tell Script to use pythonw.exe ?]

On Wed, Jul 3, 2013 at 4:11 PM, Dennis Lee Bieber wlfr...@ix.netcom.com wrote: On 03 Jul 2013 13:19:26 GMT, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info declaimed the following: On Wed, 03 Jul 2013 14:00:49 +0100, Tim Golden wrote: Goodness, I doubt if you'll find anyone who can

Re: How to tell Script to use pythonw.exe ?

On 4/07/2013 2:50 AM, Νίκος wrote: I dont understand you. I explicitly state via cmd to have the .html files opened with Chrome instead of IE. Tried it with the way you said and evben with open with.. but all that fails. some seriosu damaged must have happened and assoc are refusing to change.

[issue13582] IDLE and pythonw.exe stderr problem

Dev Player added the comment: I may be mistaken but I thought, as of not too long ago, that pythonw.exe is no longer needed by current versions. 2.7.5 -- nosy: +devplayer ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13582

[issue13582] IDLE and pythonw.exe stderr problem

Terry J. Reedy added the comment: No change. pythonw.exe is still present and in use. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13582

How to tell Script to use pythonw.exe ?

Hi, Using Windows I want to run a .py file script using pythonw.exe so the DOS box will not open. Is there a way from inside the script to say run me with pythonw.exe and not python.exe? Thanks -- http://mail.python.org/mailman/listinfo/python-list

Re: How to tell Script to use pythonw.exe ?

On 2013.07.02 20:20, goldtech wrote: Using Windows I want to run a .py file script using pythonw.exe so the DOS box will not open. Is there a way from inside the script to say run me with pythonw.exe and not python.exe? Use the .pyw extension instead of .py. Also, just FYI, DOS is long

Re: How to tell Script to use pythonw.exe ?

I just changed the file extension of the script file from .py to .pyw and it uses pythonw.exe. I didn't read it anywhere, just intuited it and tried it. Python has some very smart people working the language... -- http://mail.python.org/mailman/listinfo/python-list

Re: How to tell Script to use pythonw.exe ?

On Tue, 02 Jul 2013 18:20:12 -0700, goldtech wrote: Hi, Using Windows I want to run a .py file script using pythonw.exe so the DOS box will not open. Is there a way from inside the script to say run me with pythonw.exe and not python.exe? I don't believe so, because by the time

Re: How to tell Script to use pythonw.exe ?

goldtech leeg...@operamail.com wrote: I just changed the file extension of the script file from .py to .pyw and it uses pythonw.exe. I didn't read it anywhere, just intuited it and tried it. Python has some very smart people working the language... While your statement is true, that's not what

[issue13582] IDLE and pythonw.exe stderr problem

Terry J. Reedy added the comment: Todd, do you have a Mac to test this on? This patch treat sending messages to a widget as a backup option. In 18318 I propose we make Idle a true gui app, with all messages other than 'No tkinter' handled by the gui. Console writing, when available, would

[issue13582] IDLE and pythonw.exe stderr problem

Todd Rovito added the comment: Yes I have a Mac and I am glad to help, so I gave it a test run tonight. The first thing I did was apply the patch then I ran idle from the console like so: ./python.exe Lib/idlelib/idle.py For testing I used a simple print command to print to stderr:

[issue13582] IDLE and pythonw.exe stderr problem

Terry J. Reedy added the comment: Print in the user process goes to shell window. You need to stimulate (or just add) print or warn in the idle process, which normally goes to console, or nowhere. It is hard (intentionally, I am sure) to dynamically manipulate idle process code. Roger said

[issue13582] IDLE and pythonw.exe stderr problem

Changes by Gabriel Genellina ggenell...@gmail.com: -- nosy: +ggenellina ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13582 ___ ___

[issue18298] pythonw.exe fails with redirected stderr

anatoly techtonik added the comment: I am not using pythonw.exe, it is the option users prefer to run the program. pythonw.exe is a binary, how do you propose to patch that? Or is it translated to .exe with RPython? Can you be more specific what shell does not work correctly, what exactly

[issue18298] pythonw.exe fails with redirected stderr

Amaury Forgeot d'Arc added the comment: RPython... let's be serious. The code of pythonw.exe is very simple, see PC/WinMain.c. No, pythonw.exe is not meant to suppresses the terminal window on startup. This is only a consequence of being a windows application. There is a lot of documentation

[issue18298] pythonw.exe fails with redirected stdett

New submission from anatoly techtonik: ---cut test.py--- print(-1-) open(-2-, w).write(-3-) ---cut test.py--- C:\Python27\pythonw.exe test.py -4- type -4- -1- C:\Python27\pythonw.exe test.py 2 -4- type -4- close failed in file object destructor: sys.excepthook is missing lost sys.stderr

[issue18298] pythonw.exe fails with redirected stderr

Changes by anatoly techtonik techto...@gmail.com: -- components: +Windows ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18298 ___ ___

[issue18298] pythonw.exe fails with redirected stderr

Changes by anatoly techtonik techto...@gmail.com: -- title: pythonw.exe fails with redirected stdett - pythonw.exe fails with redirected stderr ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18298

[issue18298] pythonw.exe fails with redirected stderr

anatoly techtonik added the comment: This subprocess.communicate() call fails with pythonw.exe --cut testhg.py-- import subprocess hg = hg output, _err = subprocess.Popen([hg, 'id', '-nib'], stdout=subprocess.PIPE).communicate() open(-hg-, w).write(output) --cut testhg.py

[issue18298] pythonw.exe fails with redirected stderr

anatoly techtonik added the comment: This was meant to be a separate issue. :/ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18298 ___ ___

[issue18298] pythonw.exe fails with redirected stderr

Amaury Forgeot d'Arc added the comment: Yes, in pythonw.exe the C stderr is not really usable, and this leads to unpredictable results. It's difficult to fix in python2 though; python3 has fixed this issue, but in a way that cannot be backported. Some workarounds: - don't use pythonw.exe

[issue18298] pythonw.exe fails with redirected stderr

anatoly techtonik added the comment: It is not about modifying Python in general, it is about patching pythonw.exe or subprocess or documenting how to make subprocess calls compatible with pythonw.exe don't use pythonw.exe in a console And how to debug the issue? Maybe the only solution

[issue18298] pythonw.exe fails with redirected stderr

Amaury Forgeot d'Arc added the comment: The proper solution if you use pythonw.exe is to define sys.stdout/sys.stderr yourself in pythonw.exe:: sys.stdout = open('c:/temp/output.txt', 'w') IOW, do the redirect from inside the program, don't rely on the shell which (by design?) does

[issue13582] IDLE and pythonw.exe stderr problem

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.4 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13582 ___ ___

[issue17658] pythonw.exe crashes on opening IDLE

Roger Serwy added the comment: I'm closing this issue due since it's root problem is a misconfigured environment variable. -- resolution: - works for me status: pending - closed ___ Python tracker rep...@bugs.python.org

[issue17658] pythonw.exe crashes on opening IDLE

Roger Serwy added the comment: s/it's/its -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17658 ___ ___ Python-bugs-list mailing list

[issue17658] pythonw.exe crashes on opening IDLE

Roger Serwy added the comment: Patrick, does removing PYTHONPATH from your environment variables fix this problem? -- nosy: +roger.serwy status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17658

[issue17658] pythonw.exe crashes on opening IDLE

Amaury Forgeot d'Arc added the comment: Hum, do you have any environment variable that refer to Python27? In a terminal window (cmd.exe), try the following command: set | findstr /i python -- nosy: +amaury.forgeotdarc ___ Python tracker

  1   2   3   >