setuptools

问题 On a vanilla Plone 4.3.4 site (Unified Installer on Ubuntu 14.04.1LTS), and after updating buildout.cfg with the zopeskel and paster boiler plate stuff and running buildout, I successfully created a dexterity package in my src folder: $ cd src $ ../bin/zopeskel dexterity my.package After updating buildout.cfg (adding my.package to the eggs section and src/my.package to the develop section) and running buildout, I tried to add content to my new package, like I have done so many times in Plone

问题 I need to make a C extension with distutils (and/or setuptools) that can be used BOTH dynamically at runtime, and at compile time (for different purposes). This isn't a problem on Linux, but it's an issue on OS X. By default, distutils creates a "bundle" on OS X (and names it .so), which can be used at runtime, but NOT at compile time. I need to make a .dylib, which can be linked to at compile time, and I need to do it within a setup.py that I can package for PyPI. No matter what I try,

问题 I suffer a strange behaviour of pip. Calling pip install git+https://github.com/username/repo generally works, but on some packages it fails in an abnormal way Downloading/unpacking git+git://github.com/artscoop/django-inplaceedit Cloning git://github.com/artscoop/django-inplaceedit to /tmp/pip-rl1_7G-build Running setup.py egg_info for package from git+git://github.com/artscoop/django-inplaceedit Installing collected packages: django-inplaceedit Running setup.py install for django

问题 I am distributing a package that has this structure: mymodule: mymodule/__init__.py mymodule/code.py scripts/script1.py scripts/script2.py The mymodule subdir of mymodule contains code, and the scripts subdir contains scripts that should be executable by the user. When describing a package installation in setup.py , I use: scripts=['myscripts/script1.py'] To specify where scripts should go. During installation they typically go in some platform/user specific bin directory. The code that I

问题 I am trying to setup a Python package using setup.py . My directory structure looks like this: setup.py baxter/ __init__.py baxter.py tests/ test_baxter.py Here is setup.py : from setuptools import setup, find_packages setup(name='baxter', version='1.0', packages=find_packages() ) I first do a python setup.py build . When I then run python setup.py test I immediately get this result: running test and nothing else. The unit tests have not run since the tests take at least 15 seconds to finish

问题 This question is for Python 3.5.2, using Anaconda 4.3.0 on Windows 10 (64-bit) When I try to install packages with pip I get this error: Command "python setup.py egg_info" failed with error code 1 in C:\Users\HMGSYS\AppData\Local\Temp\pip-build-xit1wtvr\shapely\ Based on other SO answers, I tried to upgrade setuptools: pip install --upgrade setuptools But I get this error: FileNotFoundError: [WinError 2] The system cannot find the file specified: 'C:\\Users\\HMGSYS\\Anaconda3\\lib\\site

问题 I'm using conda build with a Python project that includes documentation, via a MANIFEST.in file and the package_data option to setup() : In MANIFEST.in : recursive-include pybert/doc/_build/html * In setup.py : setup( name='PyBERT', version=pybert.__version__, packages=['pybert',], package_data={'pybert': ['doc/_build/html/*',]}, I'm finding that while setup includes the subdirectories of my html directory: (pybert) Davids-Air-2:PyBERT dbanas$ tar xjf ~/anaconda/conda-bld/noarch/pybert-2.4.1

问题 I am trying to create a python package that implements a custom command class for setuptools.setup() for use in other, unrelated packages' setup.py scripts. Ideally, I would like to be able to include this package in the setup_requires argument to setup() , and have the custom command class take effect before the remainder of the setup activities are performed. Does setup() provide a hook of some sort to support this use case? If not, how can I minimize the amount of boilerplate that has to

问题 I have been following the instructions on http://docs.python-guide.org/en/latest/starting/install/osx/ but for some reason this is not going as I believe it would be expected. I have python 2.7 running by default but had to get easy_install up-to-date by following the instructions on: https://superuser.com/questions/256717/easy-install-the-wrong-version-of-python-modules-mac-os and link it from /usr/local/bin/share to /usr/local/bin. It seems to be working fine. The problem is that now when I

问题 I have a Windows 7 64bit machine and want to install the python package mgrs. I have tried using both easy_install and running python setup.py install in the mgrs directory. Easy_install gives me the error below. C:\Users\farrell>easy_install mgrs Searching for mgrs Reading https://pypi.python.org/simple/mgrs/ Best match: mgrs 1.1.0 Downloading https://pypi.python.org/packages/source/m/mgrs/mgrs-1.1.0.tar.gz#md5 =96e0c00f16d86a3f8b84c2c46cb68b8e Processing mgrs-1.1.0.tar.gz Writing c:\users