setuptools

1.安装tldr报错 （1）报错详情： [root@linuxnode1 ~]# pip install tldr Collecting tldr Downloading https://files.pythonhosted.org/packages/ff/bb/0870bf90ad1137172b3cc0758d18e99fd2325243139e0bb7652556c77e0e/tldr-0.5.tar.gz Complete output from command python setup.py egg_info: /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'long_description_markdown_filename' warnings.warn(msg) Traceback (most recent call last): File "<string>", line 1, in <module> File "/tmp/pip-build-ZBdOo2/tldr/setup.py", line 39, in <module> "Topic :: System" File "/usr/lib64/python2.7/distutils

When I run python setup.py sdist it creates an sdist in my ./dist directory. This includes a "PROJECT-egg.info" file in the zip inside my "dist" folder, which I don't use, but it doesn't hurt me, so I just ignore it. My question is why does it also create a "PROJECT-egg.info" folder in my project root directory? Can I make it stop creating this? If not, can I just delete it immediately after creating the sdist? I'm using the 'setup' function imported from setuptools. WindowsXP, Python2.7, Setuptools 0.6c11, Distribute 0.6.14. My setup config looks like: {'author': 'Jonathan Hartley', 'author

How do I package a Python module together with a precompiled .so library? Specifically, how do I write setup.py so that when I do this in Python >>> import top_secret_wrapper It can easily find top_secret.so without having to set LD_LIBRARY_PATH ? In my module development environment, I have the following file structure: . ├── top_secret_wrapper │ ├── top_secret.so │ └── __init__.py └── setup.py Inside __init__.py , I have something like: import top_secret Here's my setup.py from setuptools import setup, Extension setup( name = 'top_secret_wrapper', version = '0.1', description = 'A Python

I want to make a package to depend the particular version range e.g. >= 0.5.0, < 0.7.0 . Is it possible in install_requires option, and if so how should it be? Ricardo Altamirano According to the documentation , your syntax should work correctly. The documentation states that: setuptools and pkg_resources use a common syntax for specifying a project's required dependencies. This syntax consists of a project's PyPI name, optionally followed by a comma-separated list of "extras" in square brackets, optionally followed by a comma-separated list of version specifiers. A version specifier is one of

I'm developing an Python egg that has several .txt dependencies (they're templates used to generate files by the egg itself), and I'm struggling to get those dependencies copied to site-packages during setup.py install . According to the distribute documentation ... Filesystem of my package: setup.py package |--- __init__.py |--- main.py |--- binary (calls main.py with pkg_resources.load_entry_point) |--- templates |--file1.txt |--file2.txt In setup.py: setup( [...] eager_resources = ['templates/file1.txt', 'templates/file2.txt'] ) Within my package: from pkg_resources import resource_string

Some useful Python packages are broken on pypi, and the only acceptable version is a particular revision in a revision control system. Can that be expressed in setup.py e.g requires = 'svn://example.org/useful.package/trunk@1234' ? You need to do two things. First, require the exact version you want, e.g.: install_requires = "useful.package==1.9dev-r1234" and then include a dependency_links setting specifying where to find it: dependency_links = ["svn://example.org/useful.package/trunk@1234#egg=useful.package-1.9dev-r1234"] Note that the version #egg= part of the dependency_links URL must

I am creating a setup.py file for a project which depends on private GitHub repositories. The relevant parts of the file look like this: from setuptools import setup setup(name='my_project', ..., install_requires=[ 'public_package', 'other_public_package', 'private_repo_1', 'private_repo_2', ], dependency_links=[ 'https://github.com/my_account/private_repo_1/master/tarball/', 'https://github.com/my_account/private_repo_2/master/tarball/', ], ..., ) I am using setuptools instead of distutils because the latter does not support the install_requires and dependency_links arguments per this answer.