distutils

I am trying to integrate a third party library written in C with my python application using Cython . I have all of the python code written for a test. I am having trouble finding an example for setting this up. I have a pyd/pyx file I created manually. The third party has given me a header file (*.h) and a shared library (*.so) . As far as I can tell, there are no other dependencies. Can someone provide an example of how to set this up using Cython and disutils ? Thanks Sure ! (In the following, I assume that you already know how to deal with cimport and the interactions between .pxd and .pyx

One thing I hate about distutils (I guess he is the evil who does this ) is that it changes the shebang line. In other words, the more rational and environment-vars decided scripture #!/usr/bin/env python gets magically converted into #!/whatever/absolute/path/is/my/python This is seen also with grok: I used grokproject in a virtualenv to start my project, but now I cannot move the development directory around anymore, because it puts absolute paths in the shebang directive. The reason why I ask this is twofold I want to move it around because I started developing in one directory (Experiments

I need to run a simple script after the modules and programs have been installed. I'm having a little trouble finding straight-forward documentation on how to do this. It looks like I need to inherit from distutils.command.install, override some methods and add this object to the setup script. The specifics are a bit hazy though and it seems like a lot of effort for such a simple hook. Does anyone know an easy way to do this? I dug through distutils source for a day to learn enough about it to make a bunch of custom commands. It's not pretty, but it does work. import distutils.core from

Here's my stripped-down setup.py script with non-code stuff removed: #!/usr/bin/env python from distutils.core import setup from whyteboard.misc import meta setup( name = 'Whyteboard', version = meta.version, packages = ['whyteboard', 'whyteboard.gui', 'whyteboard.lib', 'whyteboard.lib.pubsub', 'whyteboard.lib.pubsub.core', 'whyteboard.lib.pubsub.utils', 'whyteboard.misc'], py_modules = ['whyteboard'], scripts = ['whyteboard.py'], ) MANIFEST.in: include *.txt include whyteboard-help/*.* recursive-include locale *.mo recursive-include images *.png When I run "python setup.py install sdist" I

I want to make my python package "pip installable". The problem is that the package has shell script that must be sourced in the user's init shell script (e.g. .bashrc ). But after the installation, the user don't exactly know where the script went (presumably /usr/bin , but we can't garantee). Of course the user can runs which myscript.sh and manually edits his init script. But I want to automate this step. I can create a new distutils command, but pip install doesn't call it. And I can extend distutils.command.install.install , but the installation breaks via pip (although works via python

Can I download and install Python modules from PyPi strictly inside a script, without using a shell at all ? I use a non-standard Python environment, Autodesk Maya's Python interpreter. This does not come with "easy_install," and there is no "shell," only a python script interpreter invoked by the main Maya executable. Copying and pasting ez_setup.py's contents into the script editor window and running it correctly installs an easy_install somewhere into Maya's directory, but the script incorrectly records the Python interpreter as "...maya.exe" instead of "...mayapy.exe" Furthermore, using