distutils

I vaguely remember some sort of setuptools wrapper that would generate .egg files from distutils source. Can someone jog my memory? setuptools monkey-patches some parts of distutils when it is imported. When you use easy_install to get a distutils-based project from PyPI, it will create an egg (pip may do that too). To do the same thing locally (i.e. in a directory that’s a code checkout or an unpacked tarball), use this trick: python -c "import setuptools; execfile('setup.py')" bdist_egg . Have you tried python setup.py bdist_egg Here I assume you are using setuptools instead of distutils i.e

I have a PySide application that I'm trying to package into an MSI using cx_freeze. I can successfully create an MSI installer, but I'm having trouble figuring out how to list additional modules to be included in the package. Here's my setup.py script: import sys from cx_Freeze import setup, Executable company_name = 'My Company Name' product_name = 'My Gui' bdist_msi_options = { 'upgrade_code': '{66620F3A-DC3A-11E2-B341-002219E9B01E}', 'add_to_path': False, 'initial_target_dir': r'[ProgramFilesFolder]\%s\%s' % (company_name, product_name), # 'includes': ['atexit', 'PySide.QtNetwork'], # <--

I want to create a bytecode-only distribution from distutils (no really, I do; I know what I'm doing). Using setuptools and the bdist_egg command, you can simply provide the --exclude-source parameter. Unfortunately the standard commands don't have such an option. Is there an easy way to strip the source files just before the tar.gz, zip, rpm or deb is created. Is there a relatively clean per-command way to do this (eg just for tar.gz or zip). The distutils "build_py" command is the one that matters, as it's (indirectly) reused by all the commands that create distributions. If you override the

Following an (hopefully) common practice, I have a Python package that includes several modules and an executable script in a separate scripts directory, as can be seen here . The documentation for the script, apart from the auto-generated help given by optparse, is together with the package documentation in a Sphinx subdirectory. I am trying to: generate the man page for the script from the existing documentation include the man page in the distribution I can easily do #1 with Sphinx, the man_pages setting and sphinx-build -b man . So I can call python setup.py build_sphinx -b man and have

I am trying to call a c++ code from a python script using cython. I already managed to work with an example from here but the thing is: my c++ code includes non-standard libraries from opencv. I believe I am not linking them correctly so I need someone to have a look on my setup.py and my cpp_rect.h and cpp_rect.cpp files. The error I am getting is regarding to the bold line yn the *.cpp file: cv::Mat img1(7,7,CV_32FC2,Scalar(1,3)); When I try to test the library, I receive an include error when I execute $ python userect.py : Traceback (most recent call last): File "userect.py", line 2, in

简要介绍Python模块的编译与安装。 1. setup.py编写 from distutils.core import setup setup( name='hello', version='1.0', description='A simple example', author='dbloop', author_email='984513956@qq.com', url='http://my.oschina.net/dbloop/blog', py_modules=['hello'] ) 2. 示例脚本 # coding=utf8 __metaclass__ = type __author__ = 'dbloop' print 'hello word!' 3. 编译 C:\Users\Administrator\distutilsDir\test001>python setup.py build running build running build_py creating build creating build\lib copying hello.py -> build\lib 4. 安装 C:\Users\Administrator\distutilsDir\test001>python setup.py install running install running