Use environment markers: install_requires=[ ‘threadpool >= 1.2.7; python_version < “3.2.0”‘, ] Setuptools specific usage is detailed in their documentation. The syntax shown above requires setuptools v36.2+ (change log).
The problem with the glob answer is that it only does so much. I.e. it’s not fully recursive. The problem with the copy_tree answer is that the files that are copied will be left behind on an uninstall. The proper solution is a recursive one which will let you set the package_data parameter in the … Read more
Figured it out. from cx_Freeze import setup,Executable includefiles = [‘README.txt’, ‘CHANGELOG.txt’, ‘helpers\uncompress\unRAR.exe’, , ‘helpers\uncompress\unzip.exe’] includes = [] excludes = [‘Tkinter’] packages = [‘do’,’khh’] setup( name=”myapp”, version = ‘0.1’, description = ‘A general enhancement utility’, author=”lenin”, author_email=”le…@null.com”, options = {‘build_exe’: {‘includes’:includes,’excludes’:excludes,’packages’:packages,’include_files’:includefiles}}, executables = [Executable(‘janitor.py’)] ) Note: include_files must contain “only” relative paths to the setup.py script … Read more
You could also reverse the dependency: put the version in mylib/__init__.py, parse that file in setup.py to get the version parameter, and use git tag $(setup.py –version) on the command line to create your tag. git tag -a v$(python setup.py –version) -m ‘description of version’ Is there anything more complicated you want to do that … Read more
Try setting the “CC” environment variable from inside the setup.py with os.environ.
This is the solution I ended up going with, and our apps have been running in production without any issues for close to a month with this fix in place: All I had to do was to add –ignore-installed to the pip install lines in my dockerfile that were raising errors. Using the same dockerfile … Read more
This directory is created intentionally as part of the build process for a source distribution. A little gander at the developer guide for setuptools gives you a hint as to why: But, be sure to ignore any part of the distutils documentation that deals with MANIFEST or how it’s generated from MANIFEST.in; setuptools shields you … Read more
Does this answer it? IIRC, you’ll need to use the –all flag to get rid of stuff outside of build/lib: python setup.py clean –all
If you have common code that you want to share across multiple projects, it may be worth thinking about storing this code in a physically separate project, which is then imported as a dependency into your other projects. This is easily achieved if you host your common code project in github or bitbucket, where you … Read more
You may want to use pkg_resources library that comes with setuptools. For example, I’ve made up a quick little package “proj” to illustrate the resource organization scheme I’d use: proj/setup.py proj/proj/__init__.py proj/proj/code.py proj/proj/resources/__init__.py proj/proj/resources/images/__init__.py proj/proj/resources/images/pic1.png proj/proj/resources/images/pic2.png Notice how I keep all resources in a separate subpackage. “code.py” shows how pkg_resources is used to refer to … Read more