[PyInstaller] Re: pyinstaller bug

2016-01-26 Thread Igor Futritski 
Posted it on github, issue #1801

Apparently mailing list worked, but with big delay - I was only able to see 
my post after ~10 hours.

Igor 

On Tuesday, January 26, 2016 at 1:36:14 AM UTC-8, Hartmut Goebel wrote:
>
> Am 25.01.2016 um 22:09 schrieb Igor Futritski:
>
>
> I'd like to report a bug:
>
>
> If the mailinglist does not work, please post the bug at github 
>
> -- 
> Schönen Gruß 
> Hartmut Goebel 
> Dipl.-Informatiker (univ), CISSP, CSSLP
> Information Security Management, Security Governance, Secure Software 
> Development 
>
> Goebel Consult, Landshut 
> http://www.goebel-consult.de 
>
> Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten 
> Kolumne: 
> http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht
>  
>

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] pyinstaller build fails when moved between computers

2016-01-26 Thread David J Beck 
I'm working on Macs running OS 10.11 and trying to build an app based on 
Python 3.5, Qt 5.1, and PyQt 5.1, everything installed using Homebrew 
package manager. I can build one-folder and bundled apps that run just fine 
on the computer where I have Pyinstaller, but when I move them to another 
Mac the application crashes on start up. I tried building a version with 
the -d option and when I ran it on the other computer, I got this output:

Last login: Tue Jan 26 16:15:08 on ttys000

iMonster27:~ David$ /Users/David/Desktop/dist/eFieldbook/eFieldbook ; exit;

PyInstaller Bootloader 3.x

LOADER: executable is /Users/David/Desktop/dist/eFieldbook/eFieldbook

LOADER: homepath is /Users/David/Desktop/dist/eFieldbook

LOADER: _MEIPASS2 is NULL

LOADER: archivename is /Users/David/Desktop/dist/eFieldbook/eFieldbook

LOADER: Extracting binaries

LOADER: Executing self as child

LOADER: set _MEIPASS2 to /Users/David/Desktop/dist/eFieldbook

PyInstaller Bootloader 3.x

LOADER: executable is /Users/David/Desktop/dist/eFieldbook/eFieldbook

LOADER: homepath is /Users/David/Desktop/dist/eFieldbook

LOADER: _MEIPASS2 is /Users/David/Desktop/dist/eFieldbook

LOADER: archivename is /Users/David/Desktop/dist/eFieldbook/eFieldbook

LOADER: Already in the child - running user's code.

LOADER: Python library: /Users/David/Desktop/dist/eFieldbook/Python

LOADER: Loaded functions from Python library.

LOADER: Manipulating environment (sys.path, sys.prefix)

LOADER: Pre-init sys.path is 
/Users/David/Desktop/dist/eFieldbook/base_library.zip:/Users/David/Desktop/dist/eFieldbook

LOADER: sys.prefix is /Users/David/Desktop/dist/eFieldbook

LOADER: Setting runtime options

LOADER: Initializing python

LOADER: Overriding Python's sys.path

LOADER: Post-init sys.path is 
/Users/David/Desktop/dist/eFieldbook/base_library.zip:/Users/David/Desktop/dist/eFieldbook

LOADER: Setting sys.argv

LOADER: setting sys._MEIPASS

LOADER: importing modules from CArchive

LOADER: extracted struct

LOADER: callfunction returned...

LOADER: extracted pyimod01_os_path

LOADER: callfunction returned...

LOADER: extracted pyimod02_archive

LOADER: callfunction returned...

LOADER: extracted pyimod03_importers

LOADER: callfunction returned...

LOADER: Installing PYZ archive with Python modules.

LOADER: PYZ archive: out00-PYZ.pyz

LOADER: Running pyiboot01_bootstrap.py

LOADER: Running pyi_rth_qt5.py

Illegal instruction: 4

logout

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.


[Process completed]


The crash reports this process generates look like this:


Process:   eFieldbook [988]

Path:  /Users/USER/Library/Mobile 
Documents/com~apple~CloudDocs/*/eFieldbook.app/Contents/MacOS/eFieldbook

Identifier:eFieldbook

Version:   0.0.0 (???)

Code Type: X86-64 (Native)

Parent Process:??? [987]

Responsible:   eFieldbook [988]

User ID:   501


Date/Time: 2016-01-25 14:10:19.563 -0700

OS Version:Mac OS X 10.11.2 (15C50)

Report Version:11

Anonymous UUID:12E84669-5DBC-12EB-521F-4E35DEDBB9D0



Time Awake Since Boot: 4700 seconds


System Integrity Protection: enabled


Crashed Thread:0  Dispatch queue: com.apple.main-thread


Exception Type:EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes:   0x0001, 0x

Exception Note:EXC_CORPSE_NOTIFY


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   sip.cpython-35m-darwin.so 0x000106ba9ee0 createClassType + 138

1   sip.cpython-35m-darwin.so 0x000106ba5a1f sip_api_init_module + 
680

2   PyQt5.QtCore.cpython-35m-darwin.so 0x000106311506 PyInit_QtCore + 
326

3   Python 0x000105f93448 
_PyImport_LoadDynamicModuleWithSpec + 489

4   Python 0x000105f92ffa _imp_create_dynamic + 
252

5   Python 0x000105f193b5 PyCFunction_Call + 273

6   Python 0x000105f7d530 PyEval_EvalFrameEx + 
24272

7   Python 0x000105f8026c 
_PyEval_EvalCodeWithName + 1884

8   Python 0x000105f80bab fast_function + 341

9   Python 0x000105f7cc74 PyEval_EvalFrameEx + 
22036

10  Python 0x000105f80b2b fast_function + 213

11  Python 0x000105f7cc74 PyEval_EvalFrameEx + 
22036

12  Python 0x000105f80b2b fast_function + 213

13  Python 0x000105f7cc74 PyEval_EvalFrameEx + 
22036

14  Python 0x000105f80b2b fast_function + 213

15  Python 0x000105f7cc74 PyEval_EvalFrameEx + 
22036

16  Python 0x000105f80b2b fast_function + 213

17  Python 0x000105f7cc74 PyEval_EvalFra

Re: [PyInstaller] Cant use pyinstaller

2016-01-26 Thread marcdebourget 
Hello Rafael,

as described in the link above, try to add c:\python35\scripts (adjusted to 
you real installation path) to your Windows environment PATH variable.

Best wishes,
Marc


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Cant use pyinstaller

2016-01-26 Thread marcdebourget 
Hello Rafael,

as described by the link above, this sounds like pyinstaller.py isn't found 
by the Windows environment PATH variable.
If so, you should add "c:\Python35\Scripts" (adjusted to your specific 
"Scripts" installation path) to your PATH variable.

Best wishes,
Marc

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] PyInstaller is great!

2016-01-26 Thread Parkway 
+1 and will say again that I've been using pyinstaller for a few years and 
it is just great and has become better. It is also obvious that a ton of 
effort has gone into it.

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Cant use pyinstaller

2016-01-26 Thread Hartmut Goebel 
Am 26.01.2016 um 09:54 schrieb rafael mena:
> Hello, i am trying to use pyinstaller for a simple school assignment,
> but cant get it to work.

Did you follow
?

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten
Kolumne:
http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Bundle python interpreter executable

2016-01-26 Thread Hartmut Goebel 
Am 13.01.2016 um 15:58 schrieb Jakob de Maeyer:
> In the frozen version, the subprocess line fails since it cannot find
> the 'python' executable. I see that 'python27.dll' is bundled, but
> there's no 'python.exe' (I'm trying this on Windows right now but
> it'll be cross-platform later, python version is fixed at 2.7). Is it
> possible to bundle a 'python.exe', or get a fresh interpreter in
> another fashion?

Doing this is out of PyInstaller's scope. This would mean to distribute
a complete Python distribution, which is the opposite of what
PyInstaller is doing.

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten
Kolumne:
http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] PyInstaller is great!

2016-01-26 Thread Hartmut Goebel 
Am 15.01.2016 um 22:48 schrieb jftuga:
> I just tried out PyInstaller with Python 3.5.1 on Windows 10 and it is
> fantastic.  I love using the --onefile option so that I can easily
> distribute binaries.  I will definitely be more inclined to use even
> more Python code at work now that I know I don't have to do a full
> Python install on other systems.
>
> Keep up the great work!

Thanks for the complement :-)

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten
Kolumne:
http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Examples of projects using PyInstaller

2016-01-26 Thread Hartmut Goebel 
Am 16.01.2016 um 19:10 schrieb Nicholas Chammas:
> The specific things I’m looking to see examples of in other people’s
> projects are:

You may have a look at brog -backup: https://github.com/borgbackup/borg

>   * How do they invoke PyInstaller? If they use a |.spec| file, what
> does it look like and do they check it in to their VCS?
>

As long as you can pass all required parameters on the command line, I'd
suggest *not* using a .spec-file. This eases updating for the case the
.spec-file would change or get new features.

>   * Do they restructure their project in any way to better support
> PyInstaller?
>

If you are using virtual environments, this should not be necessary.
Just setup the virtual env, install everything required into it, an run
pyinstaller.

>   * Do they use CI services like Travis and AppVeyor to automatically
> test their packaging process and generate release artifacts for
> the various OSes?
>

borg backup uses travis and Vagrant. (I personally find the later one
very interesting and adopted it for building PyInstallers bootloader.)


-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten
Kolumne:
http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

Re: [PyInstaller] Calling separate Python process

2016-01-26 Thread Hartmut Goebel 
Am 19.01.2016 um 11:35 schrieb Jakob de Maeyer:
> is it possible to invoke a separate Python process? Á la
>
> |
> subprocess.call(['python','setup.py'])
> |

No,it is not since there is no "python" executable.

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten
Kolumne:
http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] Re: pyinstaller bug

2016-01-26 Thread Hartmut Goebel 
Am 25.01.2016 um 22:09 schrieb Igor Futritski:

>
> I'd like to report a bug:

If the mailinglist does not work, please post the bug at github

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/verschlusselte-mailingslisten
Kolumne:
http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht


-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] Examples of projects using PyInstaller

2016-01-26 Thread Nicholas Chammas 


Howdy,

I’m looking for examples of projects using PyInstaller on a regular basis 
to package and release their work. I’m getting ready to make my first 
release using PyInstaller , 
and as a Python newbie I think it would be instructive for me to review how 
other people use PyInstaller as I dive in myself.

The specific things I’m looking to see examples of in other people’s 
projects are:

   - How do they invoke PyInstaller? If they use a .spec file, what does it 
   look like and do they check it in to their VCS? 
   - Do they restructure their project in any way to better support 
   PyInstaller? 
   - Do they use CI services like Travis and AppVeyor to automatically test 
   their packaging process and generate release artifacts for the various OSes? 
   - How do they instruct their users to install and invoke their 
   PyInstaller packages? 
   - What naming conventions do they use for their PyInstaller packages? 

I’m not looking for anyone to answer all these questions directly; a link 
to a project that uses PyInstaller to make releases is all I need.

Of course, if you contribute to a project that uses PyInstaller and would 
like to chime in with advice, I would welcome that too.

Nick
​

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] Calling separate Python process

2016-01-26 Thread Jakob de Maeyer 
Hi everyone,

is it possible to invoke a separate Python process? Á la

subprocess.call(['python', 'setup.py'])

but with the bootloader taking care of things. My use case is a script that 
downloads packages via pip, then needs to build an egg via "python setup.py 
bdist_egg".


Thanks,
-Jakob

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] Bundle python interpreter executable

2016-01-26 Thread Jakob de Maeyer 
Hey everyone,

I have a script (that I'd like to freeze) which generates a setup.py file, 
then calls 'python setup.py [some args]' to build a Python egg, e.g.:

# Generate setup.py here

if getattr(sys, 'frozen', False):
exe = sys.executable
else:
exe = 'python'
subprocess.check_call(
[exe, 'setup.py', 'clean', '-a', 'bdist_egg', '-d', 'build_dir'],
)

In the frozen version, the subprocess line fails since it cannot find the 
'python' executable. I see that 'python27.dll' is bundled, but there's no 
'python.exe' (I'm trying this on Windows right now but it'll be 
cross-platform later, python version is fixed at 2.7). Is it possible to 
bundle a 'python.exe', or get a fresh interpreter in another fashion?


Thanks and Cheers,
-Jakob

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] PyInstaller is great!

2016-01-26 Thread jftuga 
I just tried out PyInstaller with Python 3.5.1 on Windows 10 and it is 
fantastic.  I love using the --onefile option so that I can easily 
distribute binaries.  I will definitely be more inclined to use even more 
Python code at work now that I know I don't have to do a full Python 
install on other systems.

Keep up the great work!

Thank,
-John

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] pyinstaller ImportError: /tmp/_MEIrkqpFj/_io.so: undefined symbol: _PyLong_AsInt

2016-01-26 Thread guobb423 

I can import _io module at terminal. pyinstaller is also pass, but run the 
app, error snapshot as below.
at the sys._MEIPASS path, _io.so is also exist, i really don't know why.

Anyone face it? thank you.


Traceback (most recent call last):
  File "", line 13, in 
  File 
"/opt/ute/python/lib/python2.7/site-packages/PyInstaller-3.1-py2.7.egg/PyInstaller/loader/pyimod03_importers.py",
 
line 546, in load_module
module = imp.load_module(fullname, fp, filename, ext_tuple)
ImportError: /tmp/_MEIrkqpFj/_io.so: undefined symbol: _PyLong_AsInt

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] pyinstaller and pythonnet are not friends!

2016-01-26 Thread Igor Futritski 
Couldn't make the simple script below to compile and run on both 32 and 64 
bit systems:

import clr

print 'ok'

1. anaconda 64 bit
2. pythonnet
3. I can build an exe file: pyinstaller clr_min_test.py
4. If I run it, it complains about missing python.runtime.dll
5. if I copy python.runtime.dll .exe folder, I get:

Unhandled Exception: System.IO.FileLoadException: Could not load file or 
assembly 'Python.Runtime, Version=4.0.0.1, Culture=neutral, 
PublicKeyToken=5000fea6cba702dd' or one of its dependencies. The located 
assembly's manifest definition does not match the assembly reference. 
(Exception from HRESULT: 0x80131040)
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, 
String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, 
StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean 
throwOnFileNotFound, Boolean forIntrospection, Boolean 
suppressSecurityChecks)
   at 
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName 
assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, 
StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean 
throwOnFileNotFound, Boolean forIntrospection, Boolean 
suppressSecurityChecks)
   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
   at clrModule.initclr()

Please help.
Igor

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.

[PyInstaller] pyinstaller bug

2016-01-26 Thread Igor Futritski 
Hello Giovanni , Hartmut
,

I've tried to post on google groups - no luck - I do not see my posts!

I'd like to report a bug:

pyinstaller+pythonnet builds, but fails on execution

Here is the test program:

import clr
print 'ok'


I've tried both 32 and 64 bit -same results.
I've used python 2.7.11 fresh installs and also tried Anaconda - same
results!

Please review the messages below:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

*C:\Projects\clr_test>dir*
* Volume in drive C has no label.*
* Volume Serial Number is EAEE-BF09*

* Directory of C:\Projects\clr_test*

*01/25/2016  11:22 AM  .*
*01/25/2016  11:22 AM  ..*
*01/23/2016  01:36 PM26 clr_min_test.py*
*   1 File(s) 26 bytes*
*   2 Dir(s)  12,898,578,432 bytes free*

*C:\Projects\clr_test>pyinstaller -F clr_min_test.py*
*46 INFO: PyInstaller: 3.1*
*46 INFO: Python: 2.7.11*
*46 INFO: Platform: Windows-7-6.1.7601-SP1*
*46 INFO: wrote C:\Projects\clr_test\clr_min_test.spec*
*46 INFO: UPX is not available.*
*46 INFO: Extending PYTHONPATH with paths*
*['C:\\Projects\\clr_test', 'C:\\Projects\\clr_test']*
*46 INFO: checking Analysis*
*46 INFO: Building Analysis because out00-Analysis.toc is non existent*
*46 INFO: Initializing module dependency graph...*
*46 INFO: Initializing module graph hooks...*
*140 INFO: running Analysis out00-Analysis.toc*
*140 INFO: Adding Microsoft.VC90.CRT to dependent assemblies of final
executable*
*  required by c:\anaconda\python.exe*
*201 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.21022.8_none_18f8a87fd1919cd9.manifest*
*201 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest*
*201 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4148_none_acd0e4ffe1daef0a.manifest*
*201 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4940_none_acd19a1fe1da248a.manifest*
*201 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.6161_none_acd388d7e1d8689f.manifest*
*279 INFO: Searching for assembly
amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.3*
*0729.6161_none ...*
*279 INFO: Found manifest
C:\Windows\WinSxS\Manifests\amd64_microsoft.vc90.crt_1f*
*c8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251.manifest*
*279 INFO: Searching for file msvcr90.dll*
*279 INFO: Found file
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b*
*_9.0.30729.6161_none_08e61857a83bc251\msvcr90.dll*
*279 INFO: Searching for file msvcp90.dll*
*279 INFO: Found file
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b*
*_9.0.30729.6161_none_08e61857a83bc251\msvcp90.dll*
*279 INFO: Searching for file msvcm90.dll*
*279 INFO: Found file
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b*
*_9.0.30729.6161_none_08e61857a83bc251\msvcm90.dll*
*358 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.21022.8_none_18f8a87fd1919cd9.manifest*
*358 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest*
*358 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4148_none_acd0e4ffe1daef0a.manifest*
*358 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4940_none_acd19a1fe1da248a.manifest*
*358 INFO: Found
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.6161_none_acd388d7e1d8689f.manifest*
*358 INFO: Adding redirect Microsoft.VC90.CRT version (9, 0, 21022, 8) ->
(9, 0,*
*30729, 6161)*
*404 INFO: Analyzing C:\Projects\clr_test\clr_min_test.py*
*404 INFO: Looking for import hooks ...*
*404 INFO: Processing hook   hook-clr.py*
*404 INFO: Processing hook   hook-encodings.py*
*3028 INFO: Processing hook   hook-httplib.py*
*3028 INFO: Looking for ctypes DLLs*
*3043 INFO: Analyzing run-time hooks ...*
*3043 INFO: Looking for dynamic libraries*
*3186 INFO: Looking for eggs*
*3186 INFO: Using Python library c:\anaconda\python27.dll*
*3186 INFO: Found binding redirects:*
*[BindingRedirect(name=u'Microsoft.VC90.CRT', language=None, arch=u'amd64',
oldVe*
*rsion=(9, 0, 21022, 8), newVersion=(9, 0, 30729, 6161),
publicKeyToken=u'1fc8b3b*
*9a1e18e3b')]*
*3201 INFO: Warnings written to
C:\Projects\clr_test\build\clr_min_test\warnclr_m*
*in_test.txt*
*3247 INFO: checking PYZ*
*3247 INFO: Building PYZ because out00-PYZ.toc is non existent*
*3247 INFO: Building PYZ (ZlibArchive)
C:\Projects\clr_test\build\clr_min_test\ou*
*t00-PYZ.pyz*
*3545 INFO: checking PKG*
*3545 INFO: Building PKG because out00-PKG.

[PyInstaller] pyinstaller + pythonnet builds, but execution fails

2016-01-26 Thread Igor Futritski 
Hello,

It looks like pyinstaller and pythonnet are not "friends".

My test program (file clr_min_test.py) is 2 lines only:

*import clr*
*print 'ok'*

See messages below, where I build and then execute it.

*Microsoft Windows [Version 6.1.7601]*
*Copyright (c) 2009 Microsoft Corporation.  All rights reserved.*

*C:\Projects\clr_test>dir*
* Volume in drive C has no label.*
* Volume Serial Number is EAEE-BF09*

* Directory of C:\Projects\clr_test*

*01/25/2016  11:22 AM  .*
*01/25/2016  11:22 AM  ..*
*01/23/2016  01:36 PM26 clr_min_test.py*
*   1 File(s) 26 bytes*
*   2 Dir(s)  12,898,578,432 bytes free*

*C:\Projects\clr_test>pyinstaller -F clr_min_test.py*
*46 INFO: PyInstaller: 3.1*
*46 INFO: Python: 2.7.11*
*46 INFO: Platform: Windows-7-6.1.7601-SP1*
*46 INFO: wrote C:\Projects\clr_test\clr_min_test.spec*
*46 INFO: UPX is not available.*
*46 INFO: Extending PYTHONPATH with paths*
*['C:\\Projects\\clr_test', 'C:\\Projects\\clr_test']*
*46 INFO: checking Analysis*
*46 INFO: Building Analysis because out00-Analysis.toc is non existent*
*46 INFO: Initializing module dependency graph...*
*46 INFO: Initializing module graph hooks...*
*140 INFO: running Analysis out00-Analysis.toc*
*140 INFO: Adding Microsoft.VC90.CRT to dependent assemblies of final 
executable*
*  required by c:\anaconda\python.exe*
*201 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.21022.8_none_18f8a87fd1919cd9.manifest*
*201 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest*
*201 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4148_none_acd0e4ffe1daef0a.manifest*
*201 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4940_none_acd19a1fe1da248a.manifest*
*201 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.6161_none_acd388d7e1d8689f.manifest*
*279 INFO: Searching for assembly 
amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.3*
*0729.6161_none ...*
*279 INFO: Found manifest 
C:\Windows\WinSxS\Manifests\amd64_microsoft.vc90.crt_1f*
*c8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251.manifest*
*279 INFO: Searching for file msvcr90.dll*
*279 INFO: Found file 
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b*
*_9.0.30729.6161_none_08e61857a83bc251\msvcr90.dll*
*279 INFO: Searching for file msvcp90.dll*
*279 INFO: Found file 
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b*
*_9.0.30729.6161_none_08e61857a83bc251\msvcp90.dll*
*279 INFO: Searching for file msvcm90.dll*
*279 INFO: Found file 
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b*
*_9.0.30729.6161_none_08e61857a83bc251\msvcm90.dll*
*358 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.21022.8_none_18f8a87fd1919cd9.manifest*
*358 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest*
*358 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4148_none_acd0e4ffe1daef0a.manifest*
*358 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.4940_none_acd19a1fe1da248a.manifest*
*358 INFO: Found 
C:\Windows\WinSxS\Manifests\amd64_policy.9.0.microsoft.vc90.crt_*
*1fc8b3b9a1e18e3b_9.0.30729.6161_none_acd388d7e1d8689f.manifest*
*358 INFO: Adding redirect Microsoft.VC90.CRT version (9, 0, 21022, 8) -> 
(9, 0,*
*30729, 6161)*
*404 INFO: Analyzing C:\Projects\clr_test\clr_min_test.py*
*404 INFO: Looking for import hooks ...*
*404 INFO: Processing hook   hook-clr.py*
*404 INFO: Processing hook   hook-encodings.py*
*3028 INFO: Processing hook   hook-httplib.py*
*3028 INFO: Looking for ctypes DLLs*
*3043 INFO: Analyzing run-time hooks ...*
*3043 INFO: Looking for dynamic libraries*
*3186 INFO: Looking for eggs*
*3186 INFO: Using Python library c:\anaconda\python27.dll*
*3186 INFO: Found binding redirects:*
*[BindingRedirect(name=u'Microsoft.VC90.CRT', language=None, arch=u'amd64', 
oldVe*
*rsion=(9, 0, 21022, 8), newVersion=(9, 0, 30729, 6161), 
publicKeyToken=u'1fc8b3b*
*9a1e18e3b')]*
*3201 INFO: Warnings written to 
C:\Projects\clr_test\build\clr_min_test\warnclr_m*
*in_test.txt*
*3247 INFO: checking PYZ*
*3247 INFO: Building PYZ because out00-PYZ.toc is non existent*
*3247 INFO: Building PYZ (ZlibArchive) 
C:\Projects\clr_test\build\clr_min_test\ou*
*t00-PYZ.pyz*
*3545 INFO: checking PKG*
*3545 INFO: Building PKG because out00-PKG.toc is non existent*
*3545 INFO: Building PKG (CArchive) out00-PKG.pkg*
*3575 INFO: Redirecting Microsoft.VC90.CRT version (9, 0, 21022, 8) -> (9, 
0, 307*
*29, 6161)*
*5107 INFO: Bootloader 
c:\anaconda\lib\site-pa

[PyInstaller] Cant use pyinstaller

2016-01-26 Thread rafael mena 
Hello, i am trying to use pyinstaller for a simple school assignment, but 
cant get it to work.
This is what i have done so far:

installed pip
downloaded the .tar.gz file of PyInstaller
ran the command: "pip install pyinstaller" and waited for install

After doing that i tried to used the command pyinstaller myscript.py
but it tells me that pyinstaller is not a command, what did i do wrong?

-- 
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 pyinstaller+unsubscr...@googlegroups.com.
To post to this group, send email to pyinstaller@googlegroups.com.
Visit this group at https://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.