pyc | 易学教程

How to execute compiled python code

阅读更多关于 How to execute compiled python code

问题 I have a compiled Python file, path/program.pyc . I want to execute it with my current globals() and locals() . I tried: with open('path/program.pyc','rb') as f: code = f.read() exec(code, globals(), locals()) More specifically, what I want to have is: a.py : a = 1 # somehow run b.pyc b.py : print(a) When I run a.py , I want to see the output: 1 . Actually execfile() does exactly what I want, but it only works for .py files not .pyc files. I am looking for a version of execfile() that works

How do I compile multiple py files as one?

阅读更多关于 How do I compile multiple py files as one?

I am new to Python and am totally lost as to where to even start to get this done. I have written many small modules (a toolset for maya) that need to be compiled into on single .pyc file. Is there a module that just does this? Or can you tell me where to go to start? A tutorial? I don't even know what terms to look for. theodox You don't even need to make an egg, you can just zip up your files and put the zip file onto your python path. Maya's version of python includes the zipimport module by default so it 'just works' as long as maya can find your zip file. Here are some discussions of the

How do I compile multiple py files as one?

阅读更多关于 How do I compile multiple py files as one?

问题 I am new to Python and am totally lost as to where to even start to get this done. I have written many small modules (a toolset for maya) that need to be compiled into on single .pyc file. Is there a module that just does this? Or can you tell me where to go to start? A tutorial? I don't even know what terms to look for. 回答1: You don't even need to make an egg, you can just zip up your files and put the zip file onto your python path. Maya's version of python includes the zipimport module by

Python not interpreting changed files, using obsolete .pyc

阅读更多关于 Python not interpreting changed files, using obsolete .pyc

问题 Using the Google App Engine to develop in python yesterday it stopped running the current version of the script. Instead of executing the most recent version it seems to run the previously pre-compiled .pyc even if the .py source was changed. Error messages actually quotes the correct line from the most current source. Except if the position of the line changed, then it quotes the line which is in the place where the error occurred previously. Deleting .pyc files causes them to be recreated

pycompile for python3.2

阅读更多关于 pycompile for python3.2

问题 I am running mint 13 and have python 3.2 installed using the apt-get package management system. I also have python 2.7 installed along with 3.2 The pycompile seems to be the one that packages python 2.7 code and and throws exceptions for python 3.2 code. I have looked around and tried to install a few packages, but have not been able to find pycompile for python 3.2. How do I get pycompile work for python 3.2? 回答1: py_compile is a stdlib module that can produce byte-code given Python source.

How hard to reverse engineer .pyd files?

阅读更多关于 How hard to reverse engineer .pyd files?

After reading How do I protect Python code? , I decided to try a really simple extension module on Windows. I compiled my own extension module on Linux before, but this is the first time I compiled it on Windows. I was expecting to get a .dll file, but instead, I got a .pyd file. Docs says they are kind of same, but it must have an init[insert-module-name]() function. Is it safe to assume, it is as hard to reverse engineer them as dll files. If not, what is their hardness to reverse engineer in a scale from .pyc file to .dll files? They are, as you already found out, equivalent to DLL files

Given a python .pyc file, is there a tool that let me view the bytecode?

阅读更多关于 Given a python .pyc file, is there a tool that let me view the bytecode?

问题 A Python module is automatically compiled into a .pyc file by CPython interpreter. The .pyc file, which contains the bytecode, is in binary format (marshaled code?). Is there a GUI (or command line) tool that let me view the bytecode? 回答1: There's a visual python disassembler called PyChrisanthemum. To do it the command-line way you can use module dis (python 2.7.3, python 3.2.3), as OP already found out. 回答2: Every *.pyc file is a binary file containing next things: a four-byte magic number

Given a python .pyc file, is there a tool that let me view the bytecode?

阅读更多关于 Given a python .pyc file, is there a tool that let me view the bytecode?

A Python module is automatically compiled into a .pyc file by CPython interpreter. The .pyc file, which contains the bytecode, is in binary format (marshaled code?). Is there a GUI (or command line) tool that let me view the bytecode? There's a visual python disassembler called PyChrisanthemum . To do it the command-line way you can use module dis ( python 2.7.3 , python 3.2.3 ), as OP already found out. Seti Volkylany Every *.pyc file is a binary file containing next things: a four-byte magic number - it's simply bytes that change with each change to the marshalling code; a four-byte

How hard to reverse engineer .pyd files?

阅读更多关于 How hard to reverse engineer .pyd files?

问题 After reading How do I protect Python code? , I decided to try a really simple extension module on Windows. I compiled my own extension module on Linux before, but this is the first time I compiled it on Windows. I was expecting to get a .dll file, but instead, I got a .pyd file. Docs says they are kind of same, but it must have an init[insert-module-name]() function. Is it safe to assume, it is as hard to reverse engineer them as dll files. If not, what is their hardness to reverse engineer

Why is the 'running' of .pyc files not faster compared to .py files?

阅读更多关于 Why is the 'running' of .pyc files not faster compared to .py files?

I know the difference between a .py and a .pyc file. My question is not about how , but about why According to the docs : A program doesn’t run any faster when it is read from a .pyc or .pyo file than when it is read from a .py file; the only thing that’s faster about .pyc or .pyo files is the speed with which they are loaded. .pyc files load imports faster. But after loading the 'running' part of .pyc files takes the same time as the 'running' part in .py files? Why is is this? I would expected that bit code (.pyc) is closer to the Python Virtual Machine and thus runs faster .py files are