By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,818 Members | 1,223 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,818 IT Pros & Developers. It's quick & easy.

Pyinstaller Command line options.

P: 5
Hi Everyone,

Can anyone who is familiar with pyinstaller explain how the command line options work. Below I have an sample of my spec file:

Expand|Select|Wrap|Line Numbers
  1.  
  2. a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'), os.path.join(HOMEPATH,'support\\useUnicode.py'), './client.py'],
  3.              pathex=['C:\\initiator_build\\Ini_Builds\\client'])
  4. pyz = PYZ(a.pure)
  5. exe = EXE( pyz,
  6.           a.scripts+[('u','','OPTION')],
  7.           [('u','','OPTION')],
  8.           a.binaries+[('u', '', 'OPTION')],
  9.           name='client.exe',
  10.           debug=False,
  11.           strip=False,
  12.           upx=False,
  13.           console=True)
  14.  
As you can probably tell, I'm not really sure where the unbuffered command line option tuple goes so I kinda placed it everywhere as following examples from the documentation. A binary file is still created, but it doesn't appear to act the same way as when when running the script with the -u option through the python interpreter. What is a.scripts and how does it differ from a.binaries? What is the difference between the three different locations I placed the tuple in terms of the executable that is created?

Thanks for all the help!
May 4 '07 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.