Silly question, but pre-packaged does the commandline work in windows? I ask because passing argument works for me
ONE thing that doesn't fully is what is displayed in the terminal in windows for the packaged (some print statements, some exception errors etc..) this is for gui and cli applications. ie from what I have seen is sys.argv is not interfered with BUT stdout maybe On Wednesday, 18 September 2013 20:02:38 UTC+1, JB wrote: > > I use pyinstaller to compile a python program for both Windows and Linux. > I've recently extended my program to accept command line arguments to > provide the same functionality as the GUI. However, it seems those command > line arguments are ignored on Windows, even though they work just fine on > Linux. To be clear, I'm talking about command line arguments being passed > to the generated executable. I tested that the command line arguments work > on Windows when I run my program directly with python, before I compile > with PyInstaller. I'm using the same arguments (--onefile --windowed) on > both Windows and Linux to create the .spec file. > > Has anyone else experienced this behavior before? Does anybody have and > idea why command line arguments would work for Linux and not for Windows? > > Thanks. > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/groups/opt_out.
