I understand that setup.py uses the same CFLAGS that were used to build Python. I have a single C extension of ours that is segfaulting. I need to build it without -O2 because -O2 is optimizing out so
I am using cython for building an extension module. The module depends on an external shared library, which is found when the module is built. Further I have some pure Pyth开发者_StackOverflow中文版on
SITUATION: I have a python library, which is controlled by git, and bundled with distutils/setuptools. And I want to automatically generate version number based on git tags, both for setup.py sdist a
I\'m开发者_高级运维 trying to make a pygame executable.I will use the following setup file: from distutils.core import setup
I installed a package from git hub: pip install -e git+http://github.com/un33k/django-uuslug.git#egg=django-uuslug
I have both Visual C++ 9.0 and 10.0 installed. I have a Python extension which uses swig. The setup.py script looks something like the following:
I have a Python 3 project with the following structure: project/ +--root/ +--__init__.py +--sub/ +--__init__.py
I am trying to test a package that includes some f90 files. If I build or install and specify the fortran compiler, it works fine. However, when I try to test I get the following error:
I have a package I\'ve created in C++ and, have already compiled it into a shared library. When I link against it with my own main function, I can initialize the package by calling the initialization
My project mix pure Python code, and Cython extensions for optimization and for linking with C libraries. I have one source tree for my Python project, and one for Cython and C code. My Cython extensi