The key is to tell easy_install where the package can be downloaded. In this particular case, it can be found at the url http://github.com/mtai/python-gearman/tarball/master. However, that link by itself won’t work, because easy_install can’t tell just by looking at the URL what it’s going to get. By changing it to http://github.com/mtai/python-gearman/tarball/master#egg=gearman-2.0.0beta instead, easy_install will be … Read more
First off, I should note that it’s impossible to compile a single .so file with sub packages using Cython. So if you want sub packages, you’re going to have to generate multiple .so files, as each .so can only represent a single module. Second, it doesn’t appear that you can compile multiple Cython/Python files (I’m … Read more
Probably the best way to do this is to use the setuptools package_data directive. This does mean using setuptools (or distribute) instead of distutils, but this is a very seamless “upgrade”. Here’s a full (but untested) example: from setuptools import setup, find_packages setup( name=”your_project_name”, version=’0.1′, description=’A description.’, packages=find_packages(exclude=[‘ez_setup’, ‘tests’, ‘tests.*’]), package_data={”: [‘license.txt’]}, include_package_data=True, install_requires=[], ) … Read more
As of May 2022, most of the other answers to this question are several years out-of-date. When you come across advice on Python packaging issues, remember to look at the date of publication, and don’t trust out-of-date information. The Python Packaging User Guide is worth a read. Every page has a “last updated” date displayed, … Read more
I realize that this is an old question, but for people finding their way here via Google: package_data is a low-down, dirty lie. It is only used when building binary packages (python setup.py bdist …) but not when building source packages (python setup.py sdist …). This is, of course, ridiculous — one would expect that … Read more