setuptools

Is there any way to tell setuptools or distribute to require a package on a specific platform? In my specific case, I'm using readline , which comes as part of the standard library on Unix systems, but on Windows I need the pyreadline module to replace that functionality (cf. this question ). If I just put it in the requirements It also installs on Unix systems where it's completely useless. setup.py is simply a python script. You can create dynamic dependencies in that script: import platform setup_requires = ['foo', 'bar'] if platform.system() == 'Windows': setup_requires.append('pyreadline'

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: After brew install python , the following comes up: Pip and setuptools have been installed. To update them pip2 install --upgrade pip setuptools Running pip2 install pip2 install --upgrade pip setuptools Traceback (most recent call last): File "/usr/local/bin/pip2", line 11, in <module> load_entry_point('pip==9.0.1', 'console_scripts', 'pip2')() File "/Users/user1/Library/Python/2.7/lib/python/site-packages/pkg_resources/__init__.py", line 564, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/Users/user1

I'm developing my first Python distribution package. My learning curve on Python packaging seems to be leveling off a bit, but I'm still wrestling with a few open questions. One is whether I should cause my unit tests to be installed alongside my code. I understand it's important to include tests in a source distribution . What I'm wondering is whether I should actually configure them to be installed? I've seen at least one popular package that appears to do this on purpose ( PyHamcrest ), and at least one other that appears to do it by accident ( behave ). So my (multi-part) question is this:

From time to time I come across a situation where I have a package that can depend on either package A or B. For example, my project depends on a package called spam , if this project is renamed to pyspam , my project can either depend on spam or pyspam . I cannot figure out (or find) how I would define such dependencies in setup.py. What is a commonly accepted way to solve this? EDIT: I would like to define the dependencies in setup.py . Something like this: from setuptools import setup setup( name='myproject', install_requires=[ 'spam || pyspam' ] ) You can check to see if the package is

Is there no sane way to peform a scripted install of binary python packages for windows? Unfortunately it seems like several essential windows python packages like pywin32 and py2exe are only available as EXE's not MSI's (and as far as I know only the latter are scriptable). Easy_install/pip also seems no use since they apparently only find source packages and then try to compile locally which is obviously unsatisfactory. Am I missing something? You can download the source code of pywin32 at sourceforge.net/projects/pywin32/files/ and then build it as MSI file yourself. Therefore you need

I've got a python module that calls an external binary, built from C source. The source for that external executable is part of my python module, distributed as a .tar.gz file. Is there a way of unzipping, then compiling that external executable, and installing it using setuptools/setup.py? What I'd like to achieve is: installing that binary into virtual environments manage compilation/installation of the binary using setup.py install , setup.py build etc. making the binary part of my python module, so that it can be distributed as a wheel without external dependencies Solved in the end by