Fatal Error Bz2 Pyd
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping http://productforums.google.com/d/topic/drive/DHP-eUZTELs each other. Join them; it only takes a minute: Sign up Error with running Python executable from script.py up vote 0 down vote favorite I created an executable .exe from a .py file using the latest version of cx_freeze for Python 2.7 with the following setup.py file: import sys from cx_Freeze import setup, Executable setup( name = "Any", http://stackoverflow.com/questions/20897494/error-with-running-python-executable-from-script-py version = "1.0", description = "Any", executables = [Executable("D:\\script.pyw", base = "Win32GUI")]) I ran it from command line: python setup.py build Then I got the executable file in the build directory as expected. It ran perfectly. Now, If I move the executable file into a different directory on the same computer. I get the following error dialog: My guess is that I need to embed something into the executable file to make it work not only on my computer but on any other computer where Python is not installed by changing something in the setup.py file. What could be it missing? python python-2.7 cx-freeze share|improve this question asked Jan 3 '14 at 5:58 cpx 7,5351154101 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted I am building compiled executable as follows. Using following versions: OS: Windows-7-6.1.7601-SP1 Python: 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] cx_Freeze: 4.2.3 I have this code hello_tkinter.py: from Tkinter import * import ttk class Main(Tk): def __init__(self,
Sign in Pricing Blog Support Search GitHub This repository Watch 100 Star 913 Fork 308 conda/conda Code Issues 1,111 Pull requests 21 Projects 0 Wiki Pulse Graphs New issue conda install ipython breaks conda (Windows 64-bit, Python 3.3) #396 Closed pfmoore opened this Issue Dec 3, 2013 · 7 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 4 participants pfmoore commented Dec 3, 2013 Running conda install ipython (which reinstalls pyyaml) on Windows 64-bit in a virtualenv, breaks pyyaml (and hence conda). I'm using the standard python.org build of Python 3.3. See the following output: PS 09:00 C:\Work\Scratch >virtualenv conda-test Using base prefix 'C:\\Apps\\Python33' New python executable in conda-test\Scripts\python.exe Installing setuptools, pip...done. PS 09:01 C:\Work\Scratch >conda-test\scripts\activate (conda-test) PS 09:01 C:\Work\Scratch >pip install conda Downloading/unpacking conda Running setup.py (path:C:\Work\Scratch\conda-test\build\conda\setup.py) egg_info for package conda Not SVN Repository Downloading/unpacking pycosat (from conda) Running setup.py (path:C:\Work\Scratch\conda-test\build\pycosat\setup.py) egg_info for package pycosat Not SVN Repository Downloading/unpacking pyyaml (from conda) Running setup.py (path:C:\Work\Scratch\conda-test\build\pyyaml\setup.py) egg_info for package pyyaml Not SVN Repository Installing collected packages: conda, pycosat, pyyaml Running setup.py install for conda Not SVN Repository Installing conda-script.py script to C:\Work\Scratch\conda-test\Scripts Installing conda.exe script to C:\Work\Scratch\conda-test\Scripts Running setup.py install for pycosat building 'pycosat' extension c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\cl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -IC:\Apps\Python33\include -IC:\Apps\Python33\include /Tcpycosat.c /Fobuild\temp.win-amd64-3.3\Release\pycosat.obj pycosat.c c:\work\scratch\conda-test\build\pycosat\picosat.c(828) : warning C4244: '=' : conversion from 'unsigned __int64' to 'unsigned int', possible loss of data [lots more lines like this] c:\work\scratch\conda-test\build\pycosat\picosat.c(8271) : warning C4146: unary minus operator applied to unsigned type, result still unsigned c:\work\scratch\conda-test\build\pycosat\picosat.c(8303) : warning C4146: unary minus operator applied to unsigned type, result still unsigned c:\Program File