标签归档：pypi

知识问答

在Markdown和reStructuredText中都具有相同的自述文件

问题：在Markdown和reStructuredText中都具有相同的自述文件

我有一个托管在GitHub上的项目。为此，我使用Markdown语法编写了自述文件，以便在GitHub上很好地格式化它。

由于我的项目使用Python，因此我还计划将其上传到PyPi。PyPi上用于README的语法为reStructuredText。

我希望避免处理两个包含大致相同内容的自述文件。因此，我搜索了RST（或相反）转换器的降价促销，但找不到任何商品。

我看到的另一个解决方案是执行markdown / HTML，然后执行HTML / RST转换。我在这里和这里都找到了一些资源，所以我猜应该是可行的。

您有什么想法可以更好地适合我的工作吗？

点击查看英文原文

I have a project hosted on GitHub. For this I have written my README using the Markdown syntax in order to have it nicely formatted on GitHub.

As my project is in Python I also plan to upload it to PyPi. The syntax used for READMEs on PyPi is reStructuredText.

I would like to avoid having to handle two READMEs containing roughly the same content; so I searched for a markdown to RST (or the other way around) translator, but couldn’t find any.

The other solution I see is to perform a markdown/HTML and then a HTML/RST translation. I found some ressources for this here and here so I guess it should be possible.

Would you have any idea that could fit better with what I want to do?

回答 0

我会推荐Pandoc，“将文件从一种标记格式转换为另一种格式的瑞士军刀”（在页面底部查看受支持的转换图，这是非常令人印象深刻的）。Pandoc允许markdown直接进行reStructuredText翻译。此外，还有一个在线编辑器，在这里它可以让你尝试一下，所以你可以简单地使用在线编辑器来转换你的自述文件。

点击查看英文原文

I would recommend Pandoc, the “swiss-army knife for converting files from one markup format into another” (check out the diagram of supported conversions at the bottom of the page, it is quite impressive). Pandoc allows markdown to reStructuredText translation directly. There is also an online editor here which lets you try it out, so you could simply use the online editor to convert your README files.

回答 1

正如@Chris建议的那样，您可以使用Pandoc将Markdown转换为RST。这可以使用pypandoc模块和setup.py中的一些魔术来简单地自动化：

from setuptools import setup
try:
    from pypandoc import convert
    read_md = lambda f: convert(f, 'rst')
except ImportError:
    print("warning: pypandoc module not found, could not convert Markdown to RST")
    read_md = lambda f: open(f, 'r').read()

setup(
    # name, version, ...
    long_description=read_md('README.md'),
    install_requires=[]
)

对于在PyPi上使用的详细说明，这将自动将README.md转换为RST。当pypandoc不可用时，它将仅读取README.md而不进行转换-不会在其他人只想构建模块而不上传到PyPi时不强迫其他人安装pypandoc。

因此，您可以像往常一样在Markdown中编写内容，而不再关心RST混乱了。;）

点击查看英文原文

As @Chris suggested, you can use Pandoc to convert Markdown to RST. This can be simply automated using pypandoc module and some magic in setup.py: 

from setuptools import setup
try:
    from pypandoc import convert
    read_md = lambda f: convert(f, 'rst')
except ImportError:
    print("warning: pypandoc module not found, could not convert Markdown to RST")
    read_md = lambda f: open(f, 'r').read()

setup(
    # name, version, ...
    long_description=read_md('README.md'),
    install_requires=[]
)

This will automatically convert README.md to RST for the long description using on PyPi. When pypandoc is not available, then it just reads README.md without the conversion – to not force others to install pypandoc when they wanna just build the module, not upload to PyPi.

So you can write in Markdown as usual and don’t care about RST mess anymore. ;)

回答 2

2019更新

PyPI Warehouse 现在也支持渲染Markdown！您只需要更新软件包配置并将其添加long_description_content_type='text/markdown'到其中即可。例如：

setup(
    name='an_example_package',
    # other arguments omitted
    long_description=long_description,
    long_description_content_type='text/markdown'
)

因此，无需再将README保留为两种格式。

您可以在文档中找到有关它的更多信息。

旧答案：

GitHub使用的标记库支持reStructuredText。这意味着您可以编写README.rst文件。

它们甚至使用code和code-block指令支持语法特定的颜色突出显示（示例）

点击查看英文原文

2019 Update

The PyPI Warehouse now supports rendering Markdown as well! You just need to update your package configuration and add the long_description_content_type='text/markdown' to it. e.g.:

setup(
    name='an_example_package',
    # other arguments omitted
    long_description=long_description,
    long_description_content_type='text/markdown'
)

Therefore, there is no need to keep the README in two formats any longer.

You can find more information about it in the documentation.

Old answer:

The Markup library used by GitHub supports reStructuredText. This means you can write a README.rst file.

They even support syntax specific color highlighting using the code and code-block directives (Example)

回答 3

PyPI现在支持Markdown进行详细描述！

在中setup.py，设置long_description为Markdown字符串，添加long_description_content_type="text/markdown"并确保您使用的是最新工具（setuptools38.6.0 +，twine1.11 +）。

有关更多详细信息，请参见Dustin Ingram的博客文章。

点击查看英文原文

PyPI now supports Markdown for long descriptions!

In setup.py, set long_description to a Markdown string, add long_description_content_type="text/markdown" and make sure you’re using recent tooling (setuptools 38.6.0+, twine 1.11+).

See Dustin Ingram’s blog post for more details.

回答 4

根据我的要求，我不想在计算机上安装Pandoc。我用了docverter。Docverter是具有HTTP接口的文档转换服务器，为此使用了Pandoc。

import requests
r = requests.post(url='http://c.docverter.com/convert',
                  data={'to':'rst','from':'markdown'},
                  files={'input_files[]':open('README.md','rb')})
if r.ok:
    print r.content
点击查看英文原文

For my requirements I didn’t want to install Pandoc in my computer. I used docverter. Docverter is a document conversion server with an HTTP interface using Pandoc for this.

import requests
r = requests.post(url='http://c.docverter.com/convert',
                  data={'to':'rst','from':'markdown'},
                  files={'input_files[]':open('README.md','rb')})
if r.ok:
    print r.content

回答 5

您可能还对以下事实感兴趣：可以编写一个公共子集，以便在以markdown呈现或以reStructuredText呈现时，文档以相同的方式出现：https: //gist.github.com/dupuy/1855764☺

点击查看英文原文

You might also be interested in the fact that it is possible to write in a common subset so that your document comes out the same way when rendered as markdown or rendered as reStructuredText: https://gist.github.com/dupuy/1855764 ☺

回答 6

我遇到了这个问题，并使用以下两个bash脚本解决了这个问题。

请注意，我已将LaTeX捆绑到Markdown中。

#!/usr/bin/env bash

if [ $# -lt 1 ]; then
  echo "$0 file.md"
  exit;
fi

filename=$(basename "$1")
extension="${filename##*.}"
filename="${filename%.*}"

if [ "$extension" = "md" ]; then
  rst=".rst"
  pandoc $1 -o $filename$rst
fi

将其转换为html也很有用。md2html：

#!/usr/bin/env bash

if [ $# -lt 1 ]; then
  echo "$0 file.md <style.css>"
  exit;
fi

filename=$(basename "$1")
extension="${filename##*.}"
filename="${filename%.*}"

if [ "$extension" = "md" ]; then
  html=".html"
  if [ -z $2 ]; then
    # if no css
    pandoc -s -S --mathjax --highlight-style pygments $1 -o $filename$html
  else
    pandoc -s -S --mathjax --highlight-style pygments -c $2 $1 -o $filename$html
  fi
fi

希望对您有所帮助

点击查看英文原文

I ran into this problem and solved it with the two following bash scripts.

Note that I have LaTeX bundled into my Markdown.

#!/usr/bin/env bash

if [ $# -lt 1 ]; then
  echo "$0 file.md"
  exit;
fi

filename=$(basename "$1")
extension="${filename##*.}"
filename="${filename%.*}"

if [ "$extension" = "md" ]; then
  rst=".rst"
  pandoc $1 -o $filename$rst
fi

Its also useful to convert to html. md2html:

#!/usr/bin/env bash

if [ $# -lt 1 ]; then
  echo "$0 file.md <style.css>"
  exit;
fi

filename=$(basename "$1")
extension="${filename##*.}"
filename="${filename%.*}"

if [ "$extension" = "md" ]; then
  html=".html"
  if [ -z $2 ]; then
    # if no css
    pandoc -s -S --mathjax --highlight-style pygments $1 -o $filename$html
  else
    pandoc -s -S --mathjax --highlight-style pygments -c $2 $1 -o $filename$html
  fi
fi

I hope that helps

回答 7

使用pandoc其他人建议的工具，我创建了一个md2rst实用程序来创建rst文件。即使此解决方案意味着您同时拥有an md和an，rst但它似乎是侵入性最小的，并且将允许将来添加任何降价支持。与更改相比setup.py，我更喜欢它，也许您也会：

#!/usr/bin/env python

'''
Recursively and destructively creates a .rst file for all Markdown
files in the target directory and below.

Created to deal with PyPa without changing anything in setup based on
the idea that getting proper Markdown support later is worth waiting
for rather than forcing a pandoc dependency in sample packages and such.

Vote for
(https://bitbucket.org/pypa/pypi/issue/148/support-markdown-for-readmes)

'''

import sys, os, re

markdown_sufs = ('.md','.markdown','.mkd')
markdown_regx = '\.(md|markdown|mkd)$'

target = '.'
if len(sys.argv) >= 2: target = sys.argv[1]

md_files = []
for root, dirnames, filenames in os.walk(target):
    for name in filenames:
        if name.endswith(markdown_sufs):
            md_files.append(os.path.join(root, name))

for md in md_files:
    bare = re.sub(markdown_regx,'',md)
    cmd='pandoc --from=markdown --to=rst "{}" -o "{}.rst"'
    print(cmd.format(md,bare))
    os.system(cmd.format(md,bare))
点击查看英文原文

Using the pandoc tool suggested by others I created a md2rst utility to create the rst files. Even though this solution means you have both an md and an rst it seemed to be the least invasive and would allow for whatever future markdown support is added. I prefer it over altering setup.py and maybe you would as well:

#!/usr/bin/env python

'''
Recursively and destructively creates a .rst file for all Markdown
files in the target directory and below.

Created to deal with PyPa without changing anything in setup based on
the idea that getting proper Markdown support later is worth waiting
for rather than forcing a pandoc dependency in sample packages and such.

Vote for
(https://bitbucket.org/pypa/pypi/issue/148/support-markdown-for-readmes)

'''

import sys, os, re

markdown_sufs = ('.md','.markdown','.mkd')
markdown_regx = '\.(md|markdown|mkd)$'

target = '.'
if len(sys.argv) >= 2: target = sys.argv[1]

md_files = []
for root, dirnames, filenames in os.walk(target):
    for name in filenames:
        if name.endswith(markdown_sufs):
            md_files.append(os.path.join(root, name))

for md in md_files:
    bare = re.sub(markdown_regx,'',md)
    cmd='pandoc --from=markdown --to=rst "{}" -o "{}.rst"'
    print(cmd.format(md,bare))
    os.system(cmd.format(md,bare))
知识问答

pypi UserWarning：未知分发选项：“ install_requires”

问题：pypi UserWarning：未知分发选项：“ install_requires”

执行python setup.py installPyPI包时，有人会遇到此警告吗？

install_requires定义软件包的要求。许多PyPI软件包都有此选项。怎么可能是“未知分发选项”？

点击查看英文原文

Does anybody encounter this warning when executing python setup.py install of a PyPI package?

install_requires defines what the package requires. A lot of PyPI packages have this option. How can it be an “unknown distribution option”?

回答 0

python setup.py使用不支持install_requires的distutils。setuptools这样做，还分发（它的后继），而pip（使用这两者之一）这样做。但是实际上您必须使用它们。即通过easy_install命令或调用setuptools pip install。

另一种方法是从setup.py中的setuptools导入安装程序，但这不是标准方法，这使得每个想要使用您的软件包的人都必须安装setuptools。

点击查看英文原文

python setup.py uses distutils which doesn’t support install_requires. setuptools does, also distribute (its successor), and pip (which uses either) do. But you actually have to use them. I.e. call setuptools through the easy_install command or pip install.

Another way is to import setup from setuptools in your setup.py, but this not standard and makes everybody wanting to use your package have to have setuptools installed.

回答 1

这是我的Google搜索的第一个结果，但没有答案。我发现升级setuptools可以为我解决问题（并且可以通过点子获得很好的效果）

pip install --upgrade pip
pip install --upgrade setuptools

希望这有助于下一个人找到此链接！

点击查看英文原文

This was the first result on my google search, but had no answer. I found that upgrading setuptools resolved the issue for me (and pip for good measure)

pip install --upgrade pip
pip install --upgrade setuptools

Hope this helps the next person to find this link!

回答 2

注意！注意！前面的答案不完善。要获取有关Python宇宙中包装状态的“最新备忘”，请阅读此相当详细的文章。

我刚尝试构建/安装ansible时遇到了这个问题。问题似乎是distutils确实不支持 install_requires。Setuptools 应该动态地对distutils进行Monkey补丁，但事实并非如此，这可能是因为setuptools的最新版本是2009年的0.6c11，而distutils是Python的核心项目。

因此，即使在手动安装setuptools-0.6c11-py2.7.egg之后运行setup.py，也只能选择distutils dist.py，而不会从site-packages / setuptools /中获取。

setuptools文档还提示您使用ez_setup而不是distutils。

但是，setuptools本身现在由分发服务器提供，setup（）的风格支持install_requires。

点击查看英文原文

ATTENTION! ATTENTION! Imperfect answer ahead. To get the “latest memo” on the state of packaging in the Python universe, read this fairly detailed essay.

I have just ran into this problem when trying to build/install ansible. The problem seems to be that distutils really doesn’t support install_requires. Setuptools should monkey-patch distutils on-the-fly, but it doesn’t, probably because the last release of setuptools is 0.6c11 from 2009, whereas distutils is a core Python project.

So even after manually installing the setuptools-0.6c11-py2.7.egg running setup.py only picks up distutils dist.py, and not the one from site-packages/setuptools/.

Also the setuptools documentation hints to using ez_setup and not distutils.

However, setuptools is itself provided by distribute nowadays, and that flavor of setup() supports install_requires.

回答 3

我在使用python 2.7.11的Mac上。我一直在创建极其简单明了的项目，我唯一的要求就是我可以运行python setup.py install，并且setup.py使用了distutils的setup命令。除了setup()我在这里提到的内容以外，除了kwargs之外，实际上没有其他导入或代码。

当我的setup.py文件导入为时，出现错误：

from distutils.core import setup

使用此功能时，我会收到诸如

/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py:267：用户警告：未知的分发选项：’entry_points’warnings.warn（味精）

如果我将导入（以及其他内容）更改为以下内容：

from distutils.core import setup
import setuptools  # noqa

警告消失。

请注意，我没有使用setuptools，只是导入它会更改行为，以使其不再发出警告。对我来说，这是造成真正莫名其妙的差异的原因，其中我正在使用的某些项目发出这些警告，而另一些则没有。

显然，某种形式的Monkey修补正在进行中，并且受导入是否完成的影响。这可能不是每个研究此问题的人的情况，但是对于我正在工作的狭窄环境，这就是我一直在寻找的答案。

这与其他（社区）评论一致，该评论说distutils应该monkeypatch setuptools，并且在安装Ansible时遇到问题。Ansible过去似乎曾尝试允许不使用setuptools进行安装，然后再进行讨论。

https://github.com/ansible/ansible/blob/devel/setup.py

很多东西都悬而未决…但是，如果您正在寻找一个简单项目的简单答案，则可能应该只导入setuptools。

点击查看英文原文

I’m on a Mac with python 2.7.11. I have been toying with creating extremely simple and straightforward projects, where my only requirement is that I can run python setup.py install, and have setup.py use the setup command, ideally from distutils. There are literally no other imports or code aside from the kwargs to setup() other than what I note here.

I get the error when the imports for my setup.py file are:

from distutils.core import setup

When I use this, I get warnings such as

/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: ‘entry_points’ warnings.warn(msg)

If I change the imports (and nothing else) to the following:

from distutils.core import setup
import setuptools  # noqa

The warnings go away.

Note that I am not using setuptools, just importing it changes the behavior such that it no longer emits the warnings. For me, this is the cause of a truly baffling difference where some projects I’m using give those warnings, and some others do not.

Clearly, some form of monkey-patching is going on, and it is affected by whether or not that import is done. This probably isn’t the situation for everyone researching this problem, but for the narrow environment in which I’m working, this is the answer I was looking for.

This is consistent with the other (community) comment, which says that distutils should monkeypatch setuptools, and that they had the problem when installing Ansible. Ansible appears to have tried to allow installs without having setuptools in the past, and then went back on that.

https://github.com/ansible/ansible/blob/devel/setup.py

A lot of stuff is up in the air… but if you’re looking for a simple answer for a simple project, you should probably just import setuptools.

回答 4

这是distutils发出的警告，表示您没有安装setuptools。从http://pypi.python.org/pypi/setuptools安装它会删除警告。

点击查看英文原文

This is a warning from distutils, and is a sign that you do not have setuptools installed. Installing it from http://pypi.python.org/pypi/setuptools will remove the warning.

回答 5

sudo apt-get install python-dev  # for python2.x installs
sudo apt-get install python3-dev  # for python3.x installs

它将安装所有缺少的标题。它解决了我的问题

点击查看英文原文 
sudo apt-get install python-dev  # for python2.x installs
sudo apt-get install python3-dev  # for python3.x installs

It will install any missing headers. It solved my issue

回答 6

结论：

distutils不支持install_requires或entry_points，setuptools不。

变化from distutils.core import setup在setup.py到from setuptools import setup或重构你的setup.py只使用distutils功能。

我来这里是因为我没有意识到entry_points只是一个setuptools功能。

如果你在这里想转换setuptools到distutils像我这样的：

  1. install_requires从setup.py中删除，然后仅将requirements.txt与pip
  2. 更改entry_points为scripts（doc）并重构所有依赖于entry_points带有shebang和入口点的完整脚本的模块。
点击查看英文原文

In conclusion:

distutils doesn’t support install_requires or entry_points, setuptools does.

change from distutils.core import setup in setup.py to from setuptools import setup or refactor your setup.py to use only distutils features.

I came here because I hadn’t realized entry_points was only a setuptools feature.

If you are here wanting to convert setuptools to distutils like me:

  1. remove install_requires from setup.py and just use requirements.txt with pip
  2. change entry_points to scripts (doc) and refactor any modules relying on entry_points to be full scripts with shebangs and an entry point.

回答 7

据我所知，这是setuptools中的一个错误，在调用标准库中的基类之前，它没有删除setuptools的特定选项：https ://bitbucket.org/pypa/setuptools/issue/29 /避免在调用时发出用户警告

如果你有一个无条件的import setuptools在你setup.py（你应该如果使用setuptools的特定选项），那么实际上脚本没有与失败ImportError表明，setuptools的安装是否正确。

您可以按以下方式使警告静音：

python -W ignore::UserWarning:distutils.dist setup.py <any-other-args>

只要当您使用无条件导入执行此操作，如果未安装setuptools，导入将完全失败:)

（我在合并后setuptools存储库的签出中看到了相同的行为，这就是为什么我确信这是setuptools错误而不是系统配置问题的原因。我希望合并前分发也会有同样的问题）

点击查看英文原文

As far as I can tell, this is a bug in setuptools where it isn’t removing the setuptools specific options before calling up to the base class in the standard library: https://bitbucket.org/pypa/setuptools/issue/29/avoid-userwarnings-emitted-when-calling

If you have an unconditional import setuptools in your setup.py (as you should if using the setuptools specific options), then the fact the script isn’t failing with ImportError indicates that setuptools is properly installed.

You can silence the warning as follows:

python -W ignore::UserWarning:distutils.dist setup.py <any-other-args>

Only do this if you use the unconditional import that will fail completely if setuptools isn’t installed :)

(I’m seeing this same behaviour in a checkout from the post-merger setuptools repo, which is why I’m confident it’s a setuptools bug rather than a system config problem. I expect pre-merge distribute would have the same problem)

回答 8

我现在已经在使用Python2.7的旧版工具中看到了这一点，在该版本中，构建（如Dockerfile）安装了非固定的依赖项，例如pytest。PyTest放弃了对Python 2.7的支持，因此您可能需要指定版本<新软件包的发行版。

或者咬紧牙关，然后将该应用程序转换为Python 3（如果可行）。

点击查看英文原文

I’ve now seen this in legacy tools using Python2.7, where a build (like a Dockerfile) installs an unpinned dependancy, for example pytest. PyTest has dropped Python 2.7 support, so you may need to specify version < the new package release.

Or bite the bullet and convert that app to Python 3 if that is viable.

知识问答

使用Python setuptools的安装后脚本

问题：使用Python setuptools的安装后脚本

是否可以在setuptools setup.py文件中指定安装后的Python脚本文件，以便用户可以运行以下命令：

python setup.py install

在本地项目文件存档上，或

pip install <name>

对于PyPI项目，该脚本将在标准setuptools安装完成时运行吗？我希望执行可以在单个Python脚本文件中编码的安装后任务（例如，向用户传递自定义安装后消息，从其他远程源存储库中提取其他数据文件）。

几年前，我遇到了这个SO答案，它回答了该主题，听起来好像当时的共识是您需要创建一个install子命令。如果仍然是这种情况，是否可以有人提供如何执行此操作的示例，以便用户不必输入第二条命令来运行脚本？

点击查看英文原文

Is it possible to specify a post-install Python script file as part of the setuptools setup.py file so that a user can run the command:

python setup.py install

on a local project file archive, or

pip install <name>

for a PyPI project and the script will be run at the completion of the standard setuptools install? I am looking to perform post-install tasks that can be coded in a single Python script file (e.g. deliver a custom post-install message to the user, pull additional data files from a different remote source repository).

I came across this SO answer from several years ago that addresses the topic and it sounds as though the consensus at that time was that you need to create an install subcommand. If that is still the case, would it be possible for someone to provide an example of how to do this so that it is not necessary for the user to enter a second command to run the script?

回答 0

注意：以下解决方案仅在安装源分发zip或tarball或从源树以可编辑模式安装时有效。从二元轮（）安装时将无法使用.whl

此解决方案更加透明：

您将添加一些内容，setup.py并且不需要额外的文件。

另外，您还需要考虑两种不同的后安装方式。一个用于开发/可编辑模式，另一个用于安装模式。

将这两个包含安装后脚本的类添加到setup.py：

from setuptools import setup
from setuptools.command.develop import develop
from setuptools.command.install import install


class PostDevelopCommand(develop):
    """Post-installation for development mode."""
    def run(self):
        develop.run(self)
        # PUT YOUR POST-INSTALL SCRIPT HERE or CALL A FUNCTION

class PostInstallCommand(install):
    """Post-installation for installation mode."""
    def run(self):
        install.run(self)
        # PUT YOUR POST-INSTALL SCRIPT HERE or CALL A FUNCTION

并cmdclass在setup()函数中插入参数setup.py：

setup(
    ...

    cmdclass={
        'develop': PostDevelopCommand,
        'install': PostInstallCommand,
    },

    ...
)

您甚至可以在安装过程中调用shell命令，例如在本示例中进行安装前准备工作：

from setuptools import setup
from setuptools.command.develop import develop
from setuptools.command.install import install
from subprocess import check_call


class PreDevelopCommand(develop):
    """Pre-installation for development mode."""
    def run(self):
        check_call("apt-get install this-package".split())
        develop.run(self)

class PreInstallCommand(install):
    """Pre-installation for installation mode."""
    def run(self):
        check_call("apt-get install this-package".split())
        install.run(self)


setup(
    ...

PS：setuptools上没有任何预安装入口点。如果您想知道为什么没有，请阅读此讨论。

点击查看英文原文

Note: The solution below only works when installing a source distribution zip or tarball, or installing in editable mode from a source tree. It will not work when installing from a binary wheel (.whl)

This solution is more transparent:

You will make a few additions to setup.py and there is no need for an extra file.

Also you need to consider two different post-installations; one for development/editable mode and the other one for install mode.

Add these two classes that includes your post-install script to setup.py:

from setuptools import setup
from setuptools.command.develop import develop
from setuptools.command.install import install


class PostDevelopCommand(develop):
    """Post-installation for development mode."""
    def run(self):
        develop.run(self)
        # PUT YOUR POST-INSTALL SCRIPT HERE or CALL A FUNCTION

class PostInstallCommand(install):
    """Post-installation for installation mode."""
    def run(self):
        install.run(self)
        # PUT YOUR POST-INSTALL SCRIPT HERE or CALL A FUNCTION

and insert cmdclass argument to setup() function in setup.py:

setup(
    ...

    cmdclass={
        'develop': PostDevelopCommand,
        'install': PostInstallCommand,
    },

    ...
)

You can even call shell commands during installation, like in this example which does pre-installation preparation:

from setuptools import setup
from setuptools.command.develop import develop
from setuptools.command.install import install
from subprocess import check_call


class PreDevelopCommand(develop):
    """Pre-installation for development mode."""
    def run(self):
        check_call("apt-get install this-package".split())
        develop.run(self)

class PreInstallCommand(install):
    """Pre-installation for installation mode."""
    def run(self):
        check_call("apt-get install this-package".split())
        install.run(self)


setup(
    ...

P.S. there are no any pre-install entry points available on setuptools. Read this discussion if you are wondering why there is none.

回答 1

注意：以下解决方案仅在安装源分发zip或tarball或从源树以可编辑模式安装时有效。从二元轮（）安装时将无法使用.whl

当安装后脚本要求已安装软件包依赖项时，这是对我有用的唯一策略：

import atexit
from setuptools.command.install import install


def _post_install():
    print('POST INSTALL')


class new_install(install):
    def __init__(self, *args, **kwargs):
        super(new_install, self).__init__(*args, **kwargs)
        atexit.register(_post_install)


setuptools.setup(
    cmdclass={'install': new_install},
点击查看英文原文

Note: The solution below only works when installing a source distribution zip or tarball, or installing in editable mode from a source tree. It will not work when installing from a binary wheel (.whl)

This is the only strategy that has worked for me when the post-install script requires that the package dependencies have already been installed:

import atexit
from setuptools.command.install import install


def _post_install():
    print('POST INSTALL')


class new_install(install):
    def __init__(self, *args, **kwargs):
        super(new_install, self).__init__(*args, **kwargs)
        atexit.register(_post_install)


setuptools.setup(
    cmdclass={'install': new_install},

回答 2

注意：以下解决方案仅在安装源分发zip或tarball或从源树以可编辑模式安装时有效。从二元轮（）安装时将无法使用.whl

一个解决方案可能是post_setup.py在in setup.py目录中包含一个。post_setup.py将包含执行安装后功能的功能，并且setup.py只会在适当的时间导入并启动它。

在setup.py：

from distutils.core import setup
from distutils.command.install_data import install_data

try:
    from post_setup import main as post_install
except ImportError:
    post_install = lambda: None

class my_install(install_data):
    def run(self):
        install_data.run(self)
        post_install()

if __name__ == '__main__':
    setup(
        ...
        cmdclass={'install_data': my_install},
        ...
    )

在post_setup.py：

def main():
    """Do here your post-install"""
    pass

if __name__ == '__main__':
    main()

通过setup.py从其目录启动的一般想法，您将能够导入，post_setup.py否则它将启动一个空函数。

在中post_setup.py，该if __name__ == '__main__':语句允许您从命令行手动启动安装后。

点击查看英文原文

Note: The solution below only works when installing a source distribution zip or tarball, or installing in editable mode from a source tree. It will not work when installing from a binary wheel (.whl)

A solution could be to include a post_setup.py in setup.py‘s directory. post_setup.py will contain a function which does the post-install and setup.py will only import and launch it at the appropriate time.

In setup.py:

from distutils.core import setup
from distutils.command.install_data import install_data

try:
    from post_setup import main as post_install
except ImportError:
    post_install = lambda: None

class my_install(install_data):
    def run(self):
        install_data.run(self)
        post_install()

if __name__ == '__main__':
    setup(
        ...
        cmdclass={'install_data': my_install},
        ...
    )

In post_setup.py:

def main():
    """Do here your post-install"""
    pass

if __name__ == '__main__':
    main()

With the common idea of launching setup.py from its directory, you will be able to import post_setup.py else it will launch an empty function.

In post_setup.py, the if __name__ == '__main__': statement allows you to manually launch post-install from command line.

回答 3

结合@ Apalala，@ Zulu和@mertyildiran的答案；这在Python 3.5环境中对我有用：

import atexit
import os
import sys
from setuptools import setup
from setuptools.command.install import install

class CustomInstall(install):
    def run(self):
        def _post_install():
            def find_module_path():
                for p in sys.path:
                    if os.path.isdir(p) and my_name in os.listdir(p):
                        return os.path.join(p, my_name)
            install_path = find_module_path()

            # Add your post install code here

        atexit.register(_post_install)
        install.run(self)

setup(
    cmdclass={'install': CustomInstall},
...

这也使您可以访问中的软件包的安装路径install_path，以进行一些shell工作。

点击查看英文原文

Combining the answers from @Apalala, @Zulu and @mertyildiran; this worked for me in a Python 3.5 environment:

import atexit
import os
import sys
from setuptools import setup
from setuptools.command.install import install

class CustomInstall(install):
    def run(self):
        def _post_install():
            def find_module_path():
                for p in sys.path:
                    if os.path.isdir(p) and my_name in os.listdir(p):
                        return os.path.join(p, my_name)
            install_path = find_module_path()

            # Add your post install code here

        atexit.register(_post_install)
        install.run(self)

setup(
    cmdclass={'install': CustomInstall},
...

This also gives you access the to the installation path of the package in install_path, to do some shell work on.

回答 4

我认为执行后安装并保持要求的最简单方法是装饰对的调用setup(...)：

from setup tools import setup


def _post_install(setup):
    def _post_actions():
        do_things()
    _post_actions()
    return setup

setup = _post_install(
    setup(
        name='NAME',
        install_requires=['...
    )
)

这将setup()在声明时运行setup。完成需求安装后，它将运行该_post_install()功能，该功能将运行内部功能_post_actions()。

点击查看英文原文

I think the easiest way to perform the post-install, and keep the requirements, is to decorate the call to setup(...):

from setup tools import setup


def _post_install(setup):
    def _post_actions():
        do_things()
    _post_actions()
    return setup

setup = _post_install(
    setup(
        name='NAME',
        install_requires=['...
    )
)

This will run setup() when declaring setup. Once done with the requirements installation, it will run the _post_install() function, which will run the inner function _post_actions().

回答 5

如果使用atexit，则无需创建新的cmdclass。您可以直接在setup（）调用之前创建atexit寄存器。它做同样的事情。

另外，如果你需要依赖先安装，但这不是用PIP工作进行安装，因为你的atexit处理程序之前PIP移动套餐到位调用。

点击查看英文原文

If using atexit, there is no need to create a new cmdclass. You can simply create your atexit register right before the setup() call. It does the same thing.

Also, if you need dependencies to be installed first, this does not work with pip install since your atexit handler will be called before pip moves the packages into place.

回答 6

我无法通过提出的任何建议来解决问题，因此这对我有所帮助。

你可以调用功能，你想刚过安装之后运行setup()的setup.py，这样的：

from setuptools import setup

def _post_install():
    <your code>

setup(...)

_post_install()
点击查看英文原文

I wasn’t able to solve a problem with any presented recommendations, so here is what helped me.

You can call function, that you want to run after installation just after setup() in setup.py, like that:

from setuptools import setup

def _post_install():
    <your code>

setup(...)

_post_install()
知识问答

我如何让setuptools安装不在PyPI上的软件包？

问题：我如何让setuptools安装不在PyPI上的软件包？

我刚刚开始使用setuptools和virtualenv。我的软件包需要最新的python-gearman，该工具仅可从GitHub获得。PyPI上的python-gearman版本是一个旧版本。Github源代码与setuptools兼容，即具有setup.py等。是否可以通过一种方法来使setuptools下载并安装新版本，而不是在PyPI上寻找并安装旧版本？

仅供参考，新的python-gearman是http://github.com/mtai/python-gearman

点击查看英文原文

I’ve just started working with setuptools and virtualenv. My package requires the latest python-gearman that is only available from GitHub. The python-gearman version that’s on PyPI is an old one. The Github source is setuptools-compatible, i.e. has setup.py, etc. Is there a way to make setuptools download and install the new version instead of looking for it on PyPI and installing the old one?

FYI, the new python-gearman is http://github.com/mtai/python-gearman

回答 0

关键是告诉easy_install软件包可以在哪里下载。在这种情况下，可以在url http://github.com/mtai/python-gearman/tarball/master找到。但是，该链接本身不起作用，因为easy_install不能仅通过查看URL来知道它将会得到什么。

通过将其更改为http://github.com/mtai/python-gearman/tarball/master#egg=gearman-2.0.0beta，easy_install将能够识别软件包名称及其版本。

最后一步是将URL添加到包的dependency_links中，例如：

setup(
   ...
   dependency_links = ['http://github.com/mtai/python-gearman/tarball/master#egg=gearman-2.0.0beta']
)

现在，在安装您的软件包时，easy_install将发现有一个可从该URL下载的“ gearman 2.0.0beta”，如果您指定“ gearman> = 2.0.0beta”，则可以在PyPI上愉快地选择它。在你的依赖中..

（通常，完成此类操作的方法是在一个人的PyPI页面上包含指向可下载源的链接；在这种情况下，如果gearman软件包的作者已包含上述链接，则您已经设置好了通常，人们用’myproject-dev’标记开发版本，然后人们使用’myproject> = somever，== dev’的要求，因此，如果没有更高版本的软件包，easy_install将尝试查看或下载该版本。）

使用--process-dependency-links时需要指定pip。请注意，不赞成使用依赖项链接处理，在以后的版本中将删除它。

点击查看英文原文

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 able to identify the package name and its version.

The final step is to add the URL to your package’s dependency_links, e.g.:

setup(
   ...
   dependency_links = ['http://github.com/mtai/python-gearman/tarball/master#egg=gearman-2.0.0beta']
)

Now, when YOUR package is being installed, easy_install will discover that there is a “gearman 2.0.0beta” available for download from that URL, and happily pick it over the one on PyPI, if you specify “gearman>=2.0.0beta” in your dependencies..

(Normally, the way this sort of thing is done is to include a link on one’s PyPI page to the downloadable source; in this case, if the author of the gearman package had included a link like the above, you’d be already set. Typically, people mark the development version with ‘myproject-dev’ and then people use a requirement of ‘myproject>=somever,==dev’, so that if there isn’t a package of somever or higher, easy_install will try to check out or download the release.)

You’ll need to specify --process-dependency-links when using pip. Note that dependency links processing has been deprecated and will be removed in a future release.

回答 1

您可以使用该pip install protocol+location[@tag][#egg=Dependency]格式通过pip直接从源安装。

吉特

pip install git+https://github.com/username/repo.git
pip install git+https://github.com/username/repo.git@MyTag
pip install git+https://github.com/username/repo.git@MyTag#egg=ProjectName

水银

pip install hg+https://hg.myproject.org/MyProject/

SVN

pip install svn+svn://svn.myproject.org/svn/MyProject

z

pip install bzr+http://bzr.myproject.org/MyProject/trunk

支持以下协议： [+git, +svn, +hg, +bzr]

版本号

@tag 可让您指定要检出的特定版本/标签。

#egg=name 使您可以指定项目作为其他项目的依赖项。

订单必须始终为@tag#egg=name。

私人仓库

您还可以通过将协议更改为SSH（ssh://）并添加适当的用户（git@）从专用存储库进行安装：

git+ssh://git@github.com/username/my_private_repo

您也可以使用用户名/密码从私人存储库安装。

git+https://<username>:<password>@github.com/<user>/<repo>.git

Github提供了创建可循环使用的个人OAuth令牌的功能

git+https://<oauth token>:x-oauth-basic@github.com/<user>/<repo>.git

requirements.txt

requirements.txt 用于指定项目依赖项：

requirements.txt

package1
package2==1.0.2
package3>=0.0.4
git+https://github.com/username/repo.git

这些不是随软件包一起自动安装的，必须通过命令安装pip -r requirements.txt。

包括需求文件

需求文件可以包括其他需求文件：

requirements-docs.txt

sphinx
-r requirements-dev.txt

requirements-dev.txt

some-dev-tool
-r requirements.txt

requirements.txt

package1
package2==1.0.2
package3>=0.0.4
git+https://github.com/username/repo.git

setup.py

需求文件可以安装setup.py使用以下命令指定的依赖项：

-e .

setup.py也可以使用与上述相同的语法从存储库进行安装，但使用此答案中dependency_links提到的值。

参考文献：

https://pip.pypa.io/zh_CN/latest/user_guide.html#installing-packages https://pip.pypa.io/zh-CN/latest/reference/pip_install.html

点击查看英文原文

You can use the pip install protocol+location[@tag][#egg=Dependency] format to install directly from source using pip.

Git

pip install git+https://github.com/username/repo.git
pip install git+https://github.com/username/repo.git@MyTag
pip install git+https://github.com/username/repo.git@MyTag#egg=ProjectName

Mercurial

pip install hg+https://hg.myproject.org/MyProject/

SVN

pip install svn+svn://svn.myproject.org/svn/MyProject

Bzr

pip install bzr+http://bzr.myproject.org/MyProject/trunk

The following protocols are supported: [+git, +svn, +hg, +bzr]

Versions

@tag lets you specify a specific version/tag to check out.

#egg=name lets you specify what the project is as a dependency for others.

The order must always be @tag#egg=name.

Private Repositories

You can also install from private repositories by changing the protocol to SSH (ssh://) and adding an appropriate user (git@):

git+ssh://git@github.com/username/my_private_repo

You can also install from private repositories with a username / password.

git+https://<username>:<password>@github.com/<user>/<repo>.git

Github provides the ability to create personal OAuth tokens which can be cycled

git+https://<oauth token>:x-oauth-basic@github.com/<user>/<repo>.git

requirements.txt

requirements.txt is used to specify project dependencies:

requirements.txt

package1
package2==1.0.2
package3>=0.0.4
git+https://github.com/username/repo.git

These are not installed automatically with the package and must be installed with the command pip -r requirements.txt.

Including requirements files

Requirements files can include other requirements files:

requirements-docs.txt

sphinx
-r requirements-dev.txt

requirements-dev.txt

some-dev-tool
-r requirements.txt

requirements.txt

package1
package2==1.0.2
package3>=0.0.4
git+https://github.com/username/repo.git

setup.py

Requirements files can install dependencies specified in setup.py with the following command:

-e .

setup.py can also install from repositories using the same syntax as above, but using the dependency_links value as mentioned in this answer.

References:

https://pip.pypa.io/en/latest/user_guide.html#installing-packages https://pip.pypa.io/en/latest/reference/pip_install.html

回答 2

正如我刚刚做同样的事情，我发现了另一种方式来做到这一点作为pip的--process-dependency-links计划在被删除pip按照19.0 此评论。

pip 18.1包含以下功能

允许将PEP 508 URL要求用作依赖项。

从 PEP 508 的描述中，此类URL依赖项的语法如下：

基于URL的最小查找：

pip @ https://github.com/pypa/pip/archive/1.3.1.zip#sha1=da9234ee9982d4bbb3c72346a6de940a148ea686

所以在你setup.py看来

setup(
   ...
   install_requires = [
   ...
   'python-gearman @ https://github.com/mtai/python-gearman/archive/master.zip'
   ...
   ]
)

注意，该链接是一个存档文件，也可以是此答案中所述的特定版本或存储库的分支。另外，请参见使用其他存储库主机的答案。

就我所知，更新依赖关系的最简单方法是pip install -I .从目录中安装软件包时使用。

点击查看英文原文

As I just had to do the same thing, I found another way to do this as pip‘s --process-dependency-links are scheduled to be removed in pip 19.0 according to this comment.

pip 18.1 includes the following feature

Allow PEP 508 URL requirements to be used as dependencies.

From the description of PEP 508, the syntax for such URL dependencies looks like:

A minimal URL based lookup:

pip @ https://github.com/pypa/pip/archive/1.3.1.zip#sha1=da9234ee9982d4bbb3c72346a6de940a148ea686

So in your setup.py it would look like

setup(
   ...
   install_requires = [
   ...
   'python-gearman @ https://github.com/mtai/python-gearman/archive/master.zip'
   ...
   ]
)

Notice, the link is an archive file and could also be a specific release or branch of a repository as described in this answer. Also, see that answer for working with other repository hosts.

To the best of my knowledge, the easiest way to update the dependency is by using pip install -I . when installing your package from its directory.

回答 3

Vanilla setuptools不支持直接从git存储库下载，但是您可以使用该页面上的“ 下载源”链接之一，例如：

easy_install http://github.com/mtai/python-gearman/tarball/master
点击查看英文原文

Vanilla setuptools does not support downloading directly from a git repository but you can use one of the Download Source links from that page, like:

easy_install http://github.com/mtai/python-gearman/tarball/master
知识问答

在代码中安装python模块

问题：在代码中安装python模块

我需要直接在脚本中从PyPi安装软件包。也许有一些模块或distutils（distribute，pip等）功能使我可以执行类似的操作，pypi.install('requests')并且请求将被安装到我的virtualenv中。

点击查看英文原文

I need to install a package from PyPi straight within my script. Maybe there’s some module or distutils (distribute, pip etc.) feature which allows me to just execute something like pypi.install('requests') and requests will be installed into my virtualenv.

回答 0

从脚本安装软件包的官方推荐方法是通过子进程调用pip的命令行界面。pip不支持此处提出的大多数其他答案。此外，自pip v10起，所有代码都已pip._internal精确定位，以使用户清楚不允许以编程方式使用pip。

使用sys.executable，以确保您将调用相同pip与当前运行相关联。

import subprocess
import sys

def install(package):
    subprocess.check_call([sys.executable, "-m", "pip", "install", package])
点击查看英文原文

The officially recommended way to install packages from a script is by calling pip’s command-line interface via a subprocess. Most other answers presented here are not supported by pip. Furthermore since pip v10, all code has been moved to pip._internal precisely in order to make it clear to users that programmatic use of pip is not allowed.

Use sys.executable to ensure that you will call the same pip associated with the current runtime.

import subprocess
import sys

def install(package):
    subprocess.check_call([sys.executable, "-m", "pip", "install", package])

回答 1

您还可以使用类似：

import pip

def install(package):
    if hasattr(pip, 'main'):
        pip.main(['install', package])
    else:
        pip._internal.main(['install', package])

# Example
if __name__ == '__main__':
    install('argh')
点击查看英文原文

You can also use something like:

import pip

def install(package):
    if hasattr(pip, 'main'):
        pip.main(['install', package])
    else:
        pip._internal.main(['install', package])

# Example
if __name__ == '__main__':
    install('argh')

回答 2

如果要用于pip安装所需的软件包并在安装后将其导入，则可以使用以下代码：

def install_and_import(package):
    import importlib
    try:
        importlib.import_module(package)
    except ImportError:
        import pip
        pip.main(['install', package])
    finally:
        globals()[package] = importlib.import_module(package)


install_and_import('transliterate')

如果您以用户身份安装软件包，则可能会遇到不能仅导入软件包的问题。请参阅如何刷新sys.path？有关其他信息。

点击查看英文原文

If you want to use pip to install required package and import it after installation, you can use this code:

def install_and_import(package):
    import importlib
    try:
        importlib.import_module(package)
    except ImportError:
        import pip
        pip.main(['install', package])
    finally:
        globals()[package] = importlib.import_module(package)


install_and_import('transliterate')

If you installed a package as a user you can encounter the problem that you cannot just import the package. See How to refresh sys.path? for additional information.

回答 3

这应该工作：

import subprocess

def install(name):
    subprocess.call(['pip', 'install', name])
点击查看英文原文

This should work:

import subprocess

def install(name):
    subprocess.call(['pip', 'install', name])

回答 4

我在@Aaron的答案中添加了一些异常处理。

import subprocess
import sys

try:
    import pandas as pd
except ImportError:
    subprocess.check_call([sys.executable, "-m", "pip", "install", 'pandas'])
finally:
    import pandas as pd
点击查看英文原文

i added some exception handling to @Aaron’s answer.

import subprocess
import sys

try:
    import pandas as pd
except ImportError:
    subprocess.check_call([sys.executable, "-m", "pip", "install", 'pandas'])
finally:
    import pandas as pd

回答 5

您可以使用“ install_requires”选项在自己程序包的setup.py中定义从属模块。

如果您的软件包需要生成一些控制台脚本，则可以使用“ console_scripts”入口点来生成包装脚本，该脚本将被放置在“ bin”文件夹（例如您的virtualenv环境）中。

点击查看英文原文

You define the dependent module inside the setup.py of your own package with the “install_requires” option.

If your package needs to have some console script generated then you can use the “console_scripts” entry point in order to generate a wrapper script that will be placed within the ‘bin’ folder (e.g. of your virtualenv environment).

知识问答

为什么python setup.py在Travis CI上说无效命令’bdist_wheel’？

问题：为什么python setup.py在Travis CI上说无效命令’bdist_wheel’？

我的Python软件包具有一个setup.py在本地配置时可以在Ubuntu Trusty和新的Vagrant Ubuntu Trusty VM上正常运行的软件包：

sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
sudo -H pip install setuptools wheel virtualenv --upgrade

但是，当我在Travis CI Trusty Beta VM上执行相同操作时：

- sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
- curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
- sudo -H pip install setuptools wheel virtualenv --upgrade

我得到：

python2.7 setup.py bdist_wheel
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
   or: setup.py --help [cmd1 cmd2 ...]
   or: setup.py --help-commands
   or: setup.py cmd --help
error: invalid command 'bdist_wheel'

这为什么我不能在python中创建轮子？是相关的，但请注意，我正在安装滚轮并升级setuptools。

点击查看英文原文

My Python package has a setup.py which builds fine locally on Ubuntu Trusty and on a fresh Vagrant Ubuntu Trusty VM when I provision it like this:

sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
sudo -H pip install setuptools wheel virtualenv --upgrade

But when I do the same on a Travis CI Trusty Beta VM:

- sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
- curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
- sudo -H pip install setuptools wheel virtualenv --upgrade

I get:

python2.7 setup.py bdist_wheel
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
   or: setup.py --help [cmd1 cmd2 ...]
   or: setup.py --help-commands
   or: setup.py cmd --help
error: invalid command 'bdist_wheel'

This Why can I not create a wheel in python? is related but note I am installing wheel and upgrading setuptools.

回答 0

不得不安装该wheel软件包。一切都是最新的，但仍然给出错误。

pip install wheel

然后

python setup.py bdist_wheel

工作没有问题。

点击查看英文原文

Had to install the wheel package. Everything was up to date but still giving the error.

pip install wheel

then

python setup.py bdist_wheel

Worked without issues.

回答 1

pip install wheel

为我工作，但您也可以添加此内容

setup(
    ...
    setup_requires=['wheel']
)

来setup.py并保存点子安装命令

点击查看英文原文 
pip install wheel

worked for me, but you can also add this

setup(
    ...
    setup_requires=['wheel']
)

to setup.py and save yourself a pip install command

回答 2

2020年1月

浪费了2个小时。

在AWS上Ubuntu 18.04 new machine，需要进行以下安装：

sudo apt-get install gcc libpq-dev -y
sudo apt-get install python-dev  python-pip -y
sudo apt-get install python3-dev python3-pip python3-venv python3-wheel -y
pip3 install wheel

特别是最后一行是必须的。
但是，可能需要3行之前。

希望能有所帮助。

点击查看英文原文

Jan 2020

2 hours wasted.

On a AWS Ubuntu 18.04 new machine, below installations are required:

sudo apt-get install gcc libpq-dev -y
sudo apt-get install python-dev  python-pip -y
sudo apt-get install python3-dev python3-pip python3-venv python3-wheel -y
pip3 install wheel

Especially the last line is must.
However before 3 lines might be required as prerequisites.

Hope that helps.

回答 3

该问题是由于：

  • 已为Python 2.7安装了旧版本的pip（6.1.1）
  • Trusty Beta映像上安装的Python 2.7的多个副本
  • 用于Python 2.7的其他位置 sudo

这一切都有点复杂，这里https://github.com/travis-ci/travis-ci/issues/4989可以更好地解释。

我的解决方案是使用user travis而非sudo：

- pip2.7 install --upgrade --user travis pip setuptools wheel virtualenv
点击查看英文原文

This problem is due to:

  • an old version of pip (6.1.1) being installed for Python 2.7
  • multiple copies of Python 2.7 installed on the Trusty Beta image
  • a different location for Python 2.7 being used for sudo

It’s all a bit complicated and better explained here https://github.com/travis-ci/travis-ci/issues/4989.

My solution was to install with user travis instead of sudo:

- pip2.7 install --upgrade --user travis pip setuptools wheel virtualenv

回答 4

如果已经安装了所有必需的模块，则可能需要将setuptools模块导入setup.py文件中。因此，只需在setup.py文件开头添加以下行。

import setuptools
from distutils.core import setup
# other imports and setups

Wheel的文档中也提到了这一点。https://wheel.readthedocs.io/en/stable/#usage

点击查看英文原文

If you already have all the required modules installed you probably need to import the setuptools module in your setup.py file. So just add the following line at the leading of setup.py file.

import setuptools
from distutils.core import setup
# other imports and setups

This is also mentioned in wheel’s documentation. https://wheel.readthedocs.io/en/stable/#usage

回答 5

与许多建议的答案和不同的解决方案一样，此错误也很奇怪。我尝试过，添加它们。只有当我添加pip install --upgrade pip最终为我消除错误时。但是我没有时间隔离哪个是哪个，所以这只是一个问题。

点击查看英文原文

This error is weird as many proposed answers and got mixed solutions. I tried them, add them. It was only when I added pip install --upgrade pip finally removed the error for me. But I have no time to isolate which is which,so this is just fyi.

回答 6

就我而言，venv创建的wheel / pip / setuptools版本太旧了。这有效：

venv/bin/pip  install --upgrade pip wheel setuptools
点击查看英文原文

in my case, the version of wheel/pip/setuptools created by venv is too old. this works:

venv/bin/pip  install --upgrade pip wheel setuptools

回答 7

我已经wheel安装了，所以我尝试卸载并重新安装，它解决了此问题：

pip uninstall wheel
pip install wheel

奇怪的…

点击查看英文原文

I already had wheel installed so I tried to uninstall and reinstall, and it fixed the issue:

pip uninstall wheel
pip install wheel

Weird…

回答 8

我的解决方法是 apt install python3-dev

点击查看英文原文

My fix was apt install python3-dev

回答 9

在中setup.py，如果您有：

from distutils.core import setup

然后，将其更改为

from setuptools import setup

然后重新创建您的virtualenv并重新运行该命令，它应该可以工作。

点击查看英文原文

In your setup.py, if you have:

from distutils.core import setup

Then, change it to

from setuptools import setup

Then re-create your virtualenv and re-run the command, and it should work.

回答 10

尝试通过从setuptools而不是distutils.core导入安装程序来修改setup.py文件

点击查看英文原文

Try modifying the setup.py file by importing setup from setuptools instead of distutils.core

回答 11

我apt-get install python3-dev在Ubuntu中做过，并添加setup_requires=["wheel"]了setup.py

点击查看英文原文

I did apt-get install python3-dev in my Ubuntu and added setup_requires=["wheel"] in setup.py

回答 12

它帮助我按照此处的说明进行操作：

https://packaging.python.org/guides/installing-using-linux-tools/

Debian / Ubuntu

Python 2：

sudo apt install python-pip

Python 3：

sudo apt install python3-venv python3-pip
点击查看英文原文

It helped me to follow instructions in here:

https://packaging.python.org/guides/installing-using-linux-tools/

Debian/Ubuntu

Python 2:

sudo apt install python-pip

Python 3:

sudo apt install python3-venv python3-pip

回答 13

使用Ubuntu 18.04，可以通过安装python3-wheel软件包来解决此问题。

通常，它是作为对任何Python包的依赖项安装的。但是尤其是在构建容器映像时，您经常使用--no-install-recommends它，因此常常会丢失它，因此必须首先手动安装。

点击查看英文原文

Using Ubuntu 18.04 this problem can be resolved by installing the python3-wheelpackage.

Usually this is installed as a dependency on any Python package. But especially when building container images you often work with --no-install-recommends and therefore it is often missing and has to be installed manually first.

回答 14

与Travis CI无关，但是尝试jupyter在Mac OSX 10.8.5上安装时遇到了类似的问题，其他答案都没有帮助。该问题是由于为名为“pyzmq，错误消息填充了数百页。

我发现的解决方案是直接安装该软件包的旧版本：

python -m pip install pyzmq==17 --user

之后，安装jupyter成功，没有错误。

点击查看英文原文

Not related to Travis CI but I ran into similar problem trying to install jupyter on my Mac OSX 10.8.5, and none of the other answers was of help. The problem was caused by building the “wheel” for the package called pyzmq, with error messages filling hundreds of pages.

The solution I found was to directly install an older version of that package:

python -m pip install pyzmq==17 --user

After that, the installation of jupyter succeded without errors.

回答 15

如果您使用的是setup.cfg文件，请将其添加到install_require零件之前：

setup_requires =
    wheel

setup.cfg项目示例：

# setup.py
from setuptools import setup

setup()
# setup.cfg
[metadata]
name = name
version = 0.0.1
description = desc
long_description = file: README.md
long_description_content_type = text/markdown
url = url
author = author
classifiers =
    Programming Language :: Python
    Programming Language :: Python :: 3

[options]
include_package_data = true
packages = find:
setup_requires =
    wheel
install_requires =
    packages
    packages
    packages
点击查看英文原文

If you’re using setup.cfg files, add this before the install_require part:

setup_requires =
    wheel

Example of setup.cfg project :

# setup.py
from setuptools import setup

setup()

# setup.cfg
[metadata]
name = name
version = 0.0.1
description = desc
long_description = file: README.md
long_description_content_type = text/markdown
url = url
author = author
classifiers =
    Programming Language :: Python
    Programming Language :: Python :: 3

[options]
include_package_data = true
packages = find:
setup_requires =
    wheel
install_requires =
    packages
    packages
    packages
知识问答

查找使用easy_install / pip安装的所有软件包？

问题：查找使用easy_install / pip安装的所有软件包？

有没有办法找到所有通过easy_install或pip安装的Python PyPI软件包？我的意思是，排除分发工具已经安装的所有东西（在本例中为Debian上的apt-get）。

点击查看英文原文

Is there a way to find all Python PyPI packages that were installed with easy_install or pip? I mean, excluding everything that was/is installed with the distributions tools (in this case apt-get on Debian).

回答 0

pip freeze将输出已安装软件包及其版本的列表。它还允许您将那些程序包写入文件，以便以后用于设置新环境。

https://pip.pypa.io/zh_CN/stable/reference/pip_freeze/#pip-freeze

点击查看英文原文

pip freeze will output a list of installed packages and their versions. It also allows you to write those packages to a file that can later be used to set up a new environment.

https://pip.pypa.io/en/stable/reference/pip_freeze/#pip-freeze

回答 1

从1.3版本的pip开始，您现在可以使用 pip list

它具有一些有用的选项，包括显示过期软件包的能力。这是文档：https : //pip.pypa.io/en/latest/reference/pip_list/

点击查看英文原文

As of version 1.3 of pip you can now use pip list

It has some useful options including the ability to show outdated packages. Here’s the documentation: https://pip.pypa.io/en/latest/reference/pip_list/

回答 2

如果有人想知道您可以使用“ pip show”命令。

pip show [options] <package>

这将列出给定软件包的安装目录。

点击查看英文原文

If anyone is wondering you can use the ‘pip show’ command.

pip show [options] <package>

This will list the install directory of the given package.

回答 3

如果Debian在pip install默认目标上的行为类似于最近的Ubuntu版本，那就太简单了：它安装到（/usr/local/lib/而不是/usr/lib（apt默认目标））。检查/ubuntu/173323/how-do-i-detect-and-remove-python-packages-installed-via-pip/259747#259747

我是ArchLinux用户，在尝试pip时遇到了同样的问题。这是我在Arch中解决问题的方法。

find /usr/lib/python2.7/site-packages -maxdepth 2 -name __init__.py | xargs pacman -Qo | grep 'No package'

此处的关键是/usr/lib/python2.7/site-packages，这是pip安装到的目录YMMV。pacman -Qo是如何Arch的PAC卡格男人几岁检查该文件的所有权。No package是没有包拥有文件时返回的一部分error: No package owns $FILENAME。整蛊解决方法：我询问有关__init__.py，因为pacman -Qo有点懵，当涉及到目录:(

为了在其他发行版中做到这一点，您必须找出在哪里pip安装东西（仅仅sudo pip install是东西），如何查询文件的所有权（Debian / Ubuntu方法是dpkg -S）以及“没有软件包拥有该路径”返回（Debian）是什么。 / Ubuntu是no path found matching pattern）。Debian / Ubuntu用户，请注意：dpkg -S如果给它一个符号链接，它将失败。只需先使用解决即可realpath。像这样：

find /usr/local/lib/python2.7/dist-packages -maxdepth 2 -name __init__.py | xargs realpath | xargs dpkg -S 2>&1 | grep 'no path found'

Fedora用户可以尝试（感谢@eddygeek）：

find /usr/lib/python2.7/site-packages -maxdepth 2 -name __init__.py | xargs rpm -qf | grep 'not owned by any package'
点击查看英文原文

If Debian behaves like recent Ubuntu versions regarding pip install default target, it’s dead easy: it installs to /usr/local/lib/ instead of /usr/lib (apt default target). Check https://askubuntu.com/questions/173323/how-do-i-detect-and-remove-python-packages-installed-via-pip/259747#259747

I am an ArchLinux user and as I experimented with pip I met this same problem. Here’s how I solved it in Arch.

find /usr/lib/python2.7/site-packages -maxdepth 2 -name __init__.py | xargs pacman -Qo | grep 'No package'

Key here is /usr/lib/python2.7/site-packages, which is the directory pip installs to, YMMV. pacman -Qo is how Arch’s pac kage man ager checks for ownership of the file. No package is part of the return it gives when no package owns the file: error: No package owns $FILENAME. Tricky workaround: I’m querying about __init__.py because pacman -Qo is a little bit ignorant when it comes to directories :(

In order to do it for other distros, you have to find out where pip installs stuff (just sudo pip install something), how to query ownership of a file (Debian/Ubuntu method is dpkg -S) and what is the “no package owns that path” return (Debian/Ubuntu is no path found matching pattern). Debian/Ubuntu users, beware: dpkg -S will fail if you give it a symbolic link. Just resolve it first by using realpath. Like this:

find /usr/local/lib/python2.7/dist-packages -maxdepth 2 -name __init__.py | xargs realpath | xargs dpkg -S 2>&1 | grep 'no path found'

Fedora users can try (thanks @eddygeek):

find /usr/lib/python2.7/site-packages -maxdepth 2 -name __init__.py | xargs rpm -qf | grep 'not owned by any package'

回答 4

从…开始：

$ pip list

列出所有软件包。找到所需的软件包后，请使用：

$ pip show <package-name>

这将显示有关此软件包的详细信息，包括其文件夹。如果您已经知道软件包名称，则可以跳过第一部分

点击这里对PIP显示更多的信息，这里的PIP列表的详细信息。

例：

$ pip show jupyter
Name: jupyter
Version: 1.0.0
Summary: Jupyter metapackage. Install all the Jupyter components in one go.
Home-page: http://jupyter.org
Author: Jupyter Development Team
Author-email: jupyter@googlegroups.org
License: BSD
Location: /usr/local/lib/python2.7/site-packages
Requires: ipywidgets, nbconvert, notebook, jupyter-console, qtconsole, ipykernel
点击查看英文原文

Start with:

$ pip list

To list all packages. Once you found the package you want, use:

$ pip show <package-name>

This will show you details about this package, including its folder. You can skip the first part if you already know the package name

Click here for more information on pip show and here for more information on pip list.

Example:

$ pip show jupyter
Name: jupyter
Version: 1.0.0
Summary: Jupyter metapackage. Install all the Jupyter components in one go.
Home-page: http://jupyter.org
Author: Jupyter Development Team
Author-email: jupyter@googlegroups.org
License: BSD
Location: /usr/local/lib/python2.7/site-packages
Requires: ipywidgets, nbconvert, notebook, jupyter-console, qtconsole, ipykernel

回答 5

pip.get_installed_distributions() 将给出已安装软件包的列表

import pip
from os.path import join

for package in pip.get_installed_distributions():
    print(package.location) # you can exclude packages that's in /usr/XXX
    print(join(package.location, package._get_metadata("top_level.txt"))) # root directory of this package
点击查看英文原文

pip.get_installed_distributions() will give a list of installed packages

import pip
from os.path import join

for package in pip.get_installed_distributions():
    print(package.location) # you can exclude packages that's in /usr/XXX
    print(join(package.location, package._get_metadata("top_level.txt"))) # root directory of this package

回答 6

下面的程序有点慢，但是它给出了一个可以识别的格式良好的软件包列表pip。也就是说，并不是所有的人都通过“ pip”安装的，但是所有的人都应该能够通过pip进行升级。

$ pip search . | egrep -B1 'INSTALLED|LATEST'

之所以慢，是因为它列出了整个pypi存储库的内容。我提交了一张票，建议pip list提供类似的功能，但效率更高。

样本输出：（将搜索限制为所有子集而不是“。”。）

$ pip search selenium | egrep -B1 'INSTALLED|LATEST'

selenium                  - Python bindings for Selenium
  INSTALLED: 2.24.0
  LATEST:    2.25.0
--
robotframework-selenium2library - Web testing library for Robot Framework
  INSTALLED: 1.0.1 (latest)
$
点击查看英文原文

The below is a little slow, but it gives a nicely formatted list of packages that pip is aware of. That is to say, not all of them were installed “by” pip, but all of them should be able to be upgraded by pip.

$ pip search . | egrep -B1 'INSTALLED|LATEST'

The reason it is slow is that it lists the contents of the entire pypi repo. I filed a ticket suggesting pip list provide similar functionality but more efficiently.

Sample output: (restricted the search to a subset instead of ‘.’ for all.)

$ pip search selenium | egrep -B1 'INSTALLED|LATEST'

selenium                  - Python bindings for Selenium
  INSTALLED: 2.24.0
  LATEST:    2.25.0
--
robotframework-selenium2library - Web testing library for Robot Framework
  INSTALLED: 1.0.1 (latest)
$

回答 7

除了@Paul Woolcock的答案，

pip freeze > requirements.txt

将在当前位置的活动环境中创建一个包含所有已安装软件包以及已安装版本号的需求文件。跑步

pip install -r requirements.txt

将安装需求文件中指定的软件包。

点击查看英文原文

Adding to @Paul Woolcock’s answer,

pip freeze > requirements.txt

will create a requirements file with all installed packages along with the installed version numbers in the active environment at the current location. Running

pip install -r requirements.txt

will install the packages specified in the requirements file.

回答 8

较新版本的pip可以通过pip list -l或pip freeze -l（--list）执行OP所需的操作。
在Debian上（至少），手册页对此没有明确说明，而我只是在假设该功能必须存在的情况下才发现了with pip list --help。

最近有评论表明此功能在文档或现有答案中均不明显（尽管有人暗示），所以我认为应该发布。我本来希望以此作为评论，但我没有信誉点。

点击查看英文原文

Newer versions of pip have the ability to do what the OP wants via pip list -l or pip freeze -l (--list).
On Debian (at least) the man page doesn’t make this clear, and I only discovered it – under the assumption that the feature must exist – with pip list --help.

There are recent comments that suggest this feature is not obvious in either the documentation or the existing answers (although hinted at by some), so I thought I should post. I would have preferred to do so as a comment, but I don’t have the reputation points.

回答 9

请注意，如果您的计算机上安装了多个版本的Python，则每个版本可能都有一些pip版本。

根据您的关联，您可能需要非常谨慎使用以下pip命令： 

pip3 list

在运行Python3.4的地方为我工作。简单使用pip list返回错误The program 'pip' is currently not installed. You can install it by typing: sudo apt-get install python-pip。

点击查看英文原文

Take note that if you have multiple versions of Python installed on your computer, you may have a few versions of pip associated with each.

Depending on your associations, you might need to be very cautious of what pip command you use: 

pip3 list

Worked for me, where I’m running Python3.4. Simply using pip list returned the error The program 'pip' is currently not installed. You can install it by typing: sudo apt-get install python-pip.

回答 10

正如@almenon指出的那样，这不再起作用，它也不是在代码中获取包信息的支持方式。以下引发异常：

import pip
installed_packages = dict([(package.project_name, package.version) 
                           for package in pip.get_installed_distributions()])

为此，您可以import pkg_resources。这是一个例子：

import pkg_resources
installed_packages = dict([(package.project_name, package.version)
                           for package in pkg_resources.working_set])

我上线了 v3.6.5

点击查看英文原文

As @almenon pointed out, this no longer works and it is not the supported way to get package information in your code. The following raises an exception:

import pip
installed_packages = dict([(package.project_name, package.version) 
                           for package in pip.get_installed_distributions()])

To accomplish this, you can import pkg_resources. Here’s an example:

import pkg_resources
installed_packages = dict([(package.project_name, package.version)
                           for package in pkg_resources.working_set])

I’m on v3.6.5

回答 11

这是Fedora或其他rpm发行版的一线工具（基于@barraponto技巧）：

find /usr/lib/python2.7/site-packages -maxdepth 2 -name __init__.py | xargs rpm -qf | grep 'not owned by any package'

将此附加到上一个命令以获取更干净的输出：

 | sed -r 's:.*/(\w+)/__.*:\1:'
点击查看英文原文

Here is the one-liner for fedora or other rpm distros (based on @barraponto tips):

find /usr/lib/python2.7/site-packages -maxdepth 2 -name __init__.py | xargs rpm -qf | grep 'not owned by any package'

Append this to the previous command to get cleaner output:

 | sed -r 's:.*/(\w+)/__.*:\1:'

回答 12

获取site-packages/（dist-packages/如果存在）所有文件/文件夹的名称，然后使用包管理器剥离通过软件包安装的文件/文件夹名称。

点击查看英文原文

Get all file/folder names in site-packages/ (and dist-packages/ if it exists), and use your package manager to strip the ones that were installed via package.

回答 13

pip Frozen列出了所有已安装的软件包，即使不是通过pip / easy_install也是如此。在CentOs / Redhat上，找到了通过rpm安装的软件包。

点击查看英文原文

pip freeze lists all installed packages even if not by pip/easy_install. On CentOs/Redhat a package installed through rpm is found.

回答 14

如果使用Anaconda python发行版，则可以使用以下conda list命令查看通过什么方法安装了什么：

user@pc:~ $ conda list
# packages in environment at /anaconda3:
#
# Name                    Version                   Build  Channel
_ipyw_jlab_nb_ext_conf    0.1.0            py36h2fc01ae_0
alabaster                 0.7.10           py36h174008c_0
amqp                      2.2.2                     <pip>
anaconda                  5.1.0                    py36_2
anaconda-client           1.6.9                    py36_0

要获取安装者pip（可能包括pip其自身）安装的条目：

user@pc:~ $ conda list | grep \<pip
amqp                      2.2.2                     <pip>
astroid                   1.6.2                     <pip>
billiard                  3.5.0.3                   <pip>
blinker                   1.4                       <pip>
ez-setup                  0.9                       <pip>
feedgenerator             1.9                       <pip>

当然，您可能只想选择第一列即可进行处理（pip如果需要，则除外）：

user@pc:~ $ conda list | awk '$3 ~ /pip/ {if ($1 != "pip") print $1}'
amqp        
astroid
billiard
blinker
ez-setup
feedgenerator

最后，您可以获取这些值并使用以下命令pip卸载所有这些值：

user@pc:~ $ conda list | awk '$3 ~ /pip/ {if ($1 != "pip") print $1}' | xargs pip uninstall -y

请注意，使用-y标记pip uninstall来避免必须确认删除。

点击查看英文原文

If you use the Anaconda python distribution, you can use the conda list command to see what was installed by what method:

user@pc:~ $ conda list
# packages in environment at /anaconda3:
#
# Name                    Version                   Build  Channel
_ipyw_jlab_nb_ext_conf    0.1.0            py36h2fc01ae_0
alabaster                 0.7.10           py36h174008c_0
amqp                      2.2.2                     <pip>
anaconda                  5.1.0                    py36_2
anaconda-client           1.6.9                    py36_0

To grab the entries installed by pip (including possibly pip itself):

user@pc:~ $ conda list | grep \<pip
amqp                      2.2.2                     <pip>
astroid                   1.6.2                     <pip>
billiard                  3.5.0.3                   <pip>
blinker                   1.4                       <pip>
ez-setup                  0.9                       <pip>
feedgenerator             1.9                       <pip>

Of course you probably want to just select the first column, which you can do with (excluding pip if needed):

user@pc:~ $ conda list | awk '$3 ~ /pip/ {if ($1 != "pip") print $1}'
amqp        
astroid
billiard
blinker
ez-setup
feedgenerator

Finally you can grab these values and pip uninstall all of them using the following:

user@pc:~ $ conda list | awk '$3 ~ /pip/ {if ($1 != "pip") print $1}' | xargs pip uninstall -y

Note the use of the -y flag for the pip uninstall to avoid having to give confirmation to delete.

回答 15

对于那些没有安装pip的人，我在github上找到了这个快速脚本（适用于Python 2.7.13）： 

import pkg_resources
distros = pkg_resources.AvailableDistributions()
for key in distros:
  print distros[key]
点击查看英文原文

For those who don’t have pip installed, I found this quick script on github (works with Python 2.7.13): 

import pkg_resources
distros = pkg_resources.AvailableDistributions()
for key in distros:
  print distros[key]

回答 16

点列表[选项]您可以在此处查看完整的参考

点击查看英文原文

pip list [options] You can see the complete reference here

回答 17

至少对于Ubuntu（也许还有其他人）来说，这是可行的（受该线程中的上一篇文章的启发）：

printf "Installed with pip:";
pip list 2>/dev/null | gawk '{print $1;}' | while read; do pip show "${REPLY}" 2>/dev/null | grep 'Location: /usr/local/lib/python2.7/dist-packages' >/dev/null; if (( $? == 0 )); then printf " ${REPLY}"; fi; done; echo
点击查看英文原文

At least for Ubuntu (maybe also others) works this (inspired by a previous post in this thread):

printf "Installed with pip:";
pip list 2>/dev/null | gawk '{print $1;}' | while read; do pip show "${REPLY}" 2>/dev/null | grep 'Location: /usr/local/lib/python2.7/dist-packages' >/dev/null; if (( $? == 0 )); then printf " ${REPLY}"; fi; done; echo
知识问答

为什么要在easy_install上使用pip？[关闭]

问题：为什么要在easy_install上使用pip？[关闭]

一条推文中写道：

不要使用easy_install，除非您喜欢对自己的脸部进行刺伤。使用点子。

为什么要在easy_install上使用pip？难道不是PyPI和程序包作者最主要的原因吗？如果作者将废话源tarball（例如：缺少文件，没有setup.py）上传到PyPI，则pip和easy_install都将失败。除了化妆品的差异，为什么Python的人（如上面的鸣叫）似乎强烈地倾向于在点子的easy_install？

（假设我们正在谈论由社区维护的Distribute软件包中的easy_install）

点击查看英文原文

A tweet reads:

Don’t use easy_install, unless you like stabbing yourself in the face. Use pip.

Why use pip over easy_install? Doesn’t the fault lie with PyPI and package authors mostly? If an author uploads crap source tarball (eg: missing files, no setup.py) to PyPI, then both pip and easy_install will fail. Other than cosmetic differences, why do Python people (like in the above tweet) seem to strongly favor pip over easy_install?

(Let’s assume that we’re talking about easy_install from the Distribute package, that is maintained by the community)

回答 0

此处的许多答案在2015年已经过时了（尽管最初由Daniel Roseman接受的答案不是）。这是当前的状态：

  • 现在，二进制程序包以轮子（.whl文件）的形式分发-不仅在PyPI上，而且在第三方存储库中，例如Christoph Gohlke的Windows Extension Packages。pip可以处理轮子；easy_install不能。
  • 虚拟环境（由3.4内置，或者可以通过2.6添加到2.6 + / 3.1 + virtualenv）已经成为一个非常重要和突出的工具（并在官方文档中推荐）；它们pip是开箱即用的，但是甚至无法正常使用easy_install。
  • distribute包含的软件包easy_install不再维护。它的改进已setuptools合并回setuptools。尝试安装distribute只会安装setuptools。
  • easy_install 本身只是准维护的。
  • 所有的其中箱子pip用于不如easy_install从解包源树-installing，从DVCS回购等-是早已过去的; 你可以pip install .，pip install git+https://。
  • pip带有来自python.org的官方Python 2.7和3.4+软件包，pip如果您从源代码构建，则默认情况下会包含引导程序。
  • 《Python打包用户指南》已取代了有关安装，使用和构建软件包的各种文档的不完整之处。现在，Python自己的有关安装Python模块的文档符合该用户指南的要求，并明确地pip称为“首选安装程序”。
  • pip这些年来，还添加了其他新功能，这些功能将永远不会存在easy_install。例如，pip通过构建需求文件，然后在每一侧使用单个命令安装它，可以轻松克隆站点程序包。或将您的需求文件转换为本地回购以用于内部开发。等等。

我知道easy_install在2015年使用的唯一好的理由是在OS X 10.5-10.8中使用Apple预先安装的Python版本的特殊情况。从10.5开始，Apple已包含easy_install，但从10.10开始，它们仍然不包含pip。使用10.9+时，您仍然应该只使用get-pip.py，但是对于10.5-10.8，这存在一些问题，因此更容易实现sudo easy_install pip。（通常，这easy_install pip是一个坏主意；您只想在OS X 10.5-10.8上才能做到这一点。）此外，10.5-10.8包含readline以一种easy_install知道如何纠缠而pip不会纠缠的方式，因此您也想sudo easy_install readline如果要升级。

点击查看英文原文

Many of the answers here are out of date for 2015 (although the initially accepted one from Daniel Roseman is not). Here’s the current state of things:

  • Binary packages are now distributed as wheels (.whl files)—not just on PyPI, but in third-party repositories like Christoph Gohlke’s Extension Packages for Windows. pip can handle wheels; easy_install cannot.
  • Virtual environments (which come built-in with 3.4, or can be added to 2.6+/3.1+ with virtualenv) have become a very important and prominent tool (and recommended in the official docs); they include pip out of the box, but don’t even work properly with easy_install.
  • The distribute package that included easy_install is no longer maintained. Its improvements over setuptools got merged back into setuptools. Trying to install distribute will just install setuptools instead.
  • easy_install itself is only quasi-maintained.
  • All of the cases where pip used to be inferior to easy_install—installing from an unpacked source tree, from a DVCS repo, etc.—are long-gone; you can pip install ., pip install git+https://.
  • pip comes with the official Python 2.7 and 3.4+ packages from python.org, and a pip bootstrap is included by default if you build from source.
  • The various incomplete bits of documentation on installing, using, and building packages have been replaced by the Python Packaging User Guide. Python’s own documentation on Installing Python Modules now defers to this user guide, and explicitly calls out pip as “the preferred installer program”.
  • Other new features have been added to pip over the years that will never be in easy_install. For example, pip makes it easy to clone your site-packages by building a requirements file and then installing it with a single command on each side. Or to convert your requirements file to a local repo to use for in-house development. And so on.

The only good reason that I know of to use easy_install in 2015 is the special case of using Apple’s pre-installed Python versions with OS X 10.5-10.8. Since 10.5, Apple has included easy_install, but as of 10.10 they still don’t include pip. With 10.9+, you should still just use get-pip.py, but for 10.5-10.8, this has some problems, so it’s easier to sudo easy_install pip. (In general, easy_install pip is a bad idea; it’s only for OS X 10.5-10.8 that you want to do this.) Also, 10.5-10.8 include readline in a way that easy_install knows how to kludge around but pip doesn’t, so you also want to sudo easy_install readline if you want to upgrade that.

回答 1

从伊恩·比金（Ian Bicking）自己对pip的介绍：

pip最初旨在通过以下方式对easy_install进行改进

  • 所有软件包均在安装前已下载。结果不会发生部分完成的安装。
  • 注意在控制台上显示有用的输出。
  • 采取行动的原因已被跟踪。例如，如果正在安装软件包，则pip会跟踪为什么需要该软件包。
  • 错误消息应该很有用。
  • 该代码相对简洁明了，具有内聚性，可以更轻松地以编程方式使用。
  • 软件包不必作为Egg存档安装，可以将它们平放安装（同时保留Egg元数据）。
  • 对其他版本控制系统（Git，Mercurial和Bazaar）的本地支持
  • 卸载软件包。
  • 简单定义固定的需求集并可靠地复制一组包。
点击查看英文原文

From Ian Bicking’s own introduction to pip:

pip was originally written to improve on easy_install in the following ways

  • All packages are downloaded before installation. Partially-completed installation doesn’t occur as a result.
  • Care is taken to present useful output on the console.
  • The reasons for actions are kept track of. For instance, if a package is being installed, pip keeps track of why that package was required.
  • Error messages should be useful.
  • The code is relatively concise and cohesive, making it easier to use programmatically.
  • Packages don’t have to be installed as egg archives, they can be installed flat (while keeping the egg metadata).
  • Native support for other version control systems (Git, Mercurial and Bazaar)
  • Uninstallation of packages.
  • Simple to define fixed sets of requirements and reliably reproduce a set of packages.

回答 2

另一个（至今尚未提及）之所以喜欢点子，是因为它是新的热点，并将在未来继续使用。

以下信息图表（来自《The Hitchhiker’s Guide to Packaging v1.0》中的“ 包装的当前状态”部分）表明setuptools / easy_install将来会消失。

这是Distribution的文档中的另一个信息图，显示Setuptools和easy_install将被新的热点— distribution和pip取代。虽然PIP仍然是新的辣味，分发与合并的setuptools在2013年发布的setuptools V0.7。

点击查看英文原文

Another—as of yet unmentioned—reason for favoring pip is because it is the new hotness and will continue to be used in the future.

The infographic below—from the Current State of Packaging section in the The Hitchhiker’s Guide to Packaging v1.0—shows that setuptools/easy_install will go away in the future.

Here’s another infographic from distribute’s documentation showing that Setuptools and easy_install will be replaced by the new hotness—distribute and pip. While pip is still the new hotness, Distribute merged with Setuptools in 2013 with the release of Setuptools v0.7.

回答 3

有两个原因，可能还有更多：

  1. pip提供uninstall命令

  2. 如果中间安装失败，则pip将使您保持干净状态。

点击查看英文原文

Two reasons, there may be more:

  1. pip provides an uninstall command

  2. if an installation fails in the middle, pip will leave you in a clean state.

回答 4

需求文件。

认真地说，我每天都将它与virtualenv结合使用。

快速依赖管理教程，民谣

需求文件使您可以创建已通过pip安装的所有软件包的快照。通过将这些程序包封装在虚拟环境中，可以使代码库在一组非常特定的程序包中工作，并与其他人共享该代码库。

从Heroku的文档中 https://devcenter.heroku.com/articles/python

您创建一个虚拟环境，并设置您的外壳以使用它。（bash / * nix指令）

virtualenv env
source env/bin/activate

现在，与此外壳一起运行的所有python脚本都将使用该环境的软件包和配置。现在，您可以在此环境中本地安装软件包，而无需在计算机上全局安装。

pip install flask

现在，您可以转储有关安装哪些软件包的信息

pip freeze > requirements.txt

如果您将该文件签入版本控制中，那么当其他人获取您的代码时，他们可以设置自己的虚拟环境并使用以下命令安装所有依赖项：

pip install -r requirements.txt

任何时候您都可以像这样自动执行乏味的操作。

点击查看英文原文

REQUIREMENTS files.

Seriously, I use this in conjunction with virtualenv every day.

QUICK DEPENDENCY MANAGEMENT TUTORIAL, FOLKS

Requirements files allow you to create a snapshot of all packages that have been installed through pip. By encapsulating those packages in a virtualenvironment, you can have your codebase work off a very specific set of packages and share that codebase with others.

From Heroku’s documentation https://devcenter.heroku.com/articles/python

You create a virtual environment, and set your shell to use it. (bash/*nix instructions)

virtualenv env
source env/bin/activate

Now all python scripts run with this shell will use this environment’s packages and configuration. Now you can install a package locally to this environment without needing to install it globally on your machine.

pip install flask

Now you can dump the info about which packages are installed with

pip freeze > requirements.txt

If you checked that file into version control, when someone else gets your code, they can setup their own virtual environment and install all the dependencies with:

pip install -r requirements.txt

Any time you can automate tedium like this is awesome.

回答 5

pip不会安装二进制软件包，并且未在Windows上经过良好测试。

由于Windows默认没有附带编译器，因此通常无法在其中使用pip 。easy_install 可以为Windows安装二进制软件包。

点击查看英文原文

pip won’t install binary packages and isn’t well tested on Windows.

As Windows doesn’t come with a compiler by default pip often can’t be used there. easy_install can install binary packages for Windows.

回答 6

更新：正如某些人所想，setuptools已经吸收distribute了相反的东西。setuptools是最新的最新distutils更改和滚轮格式。因此，easy_install和pip或多或少平等现在。

来源：http : //pythonhosted.org/setuptools/merge-faq.html#why-setuptools-and-not-distribute-or-another-name

点击查看英文原文

UPDATE: setuptools has absorbed distribute as opposed to the other way around, as some thought. setuptools is up-to-date with the latest distutils changes and the wheel format. Hence, easy_install and pip are more or less on equal footing now.

Source: http://pythonhosted.org/setuptools/merge-faq.html#why-setuptools-and-not-distribute-or-another-name

回答 7

除了模糊人的答复：

pip不会安装二进制软件包，并且未在Windows上经过良好测试。

由于Windows默认不带编译器，因此通常无法在其中使用pip。easy_install可以为Windows安装二进制软件包。

这是Windows上的一个技巧：

  • 您可以使用easy_install <package>安装二进制软件包来避免生成二进制文件

  • pip uninstall <package>即使您使用过easy_install，也可以使用 。

这只是在Windows上对我有效的解决方法。实际上，如果不涉及二进制文件，我总是使用pip。

请参阅当前的pip doku：http：//www.pip-installer.org/en/latest/other-tools.html#pip-compared-to-easy-install

我将在邮件列表中询问为此计划的内容。

这是最新的更新：

新的受支持的安装二进制文件的方式将是wheel！它尚未在标准中，但几乎已经存在。当前版本仍为Alpha：1.0.0a1

https://pypi.python.org/pypi/wheel

http://wheel.readthedocs.org/en/latest/

我将wheel通过创建要PySide使用的OS X安装程序进行测试wheel，而不是蛋。会回来并报告此情况。

欢呼声-克里斯

快速更新：

到的过渡wheel即将结束。大多数软件包都支持wheel。

我答应为制作车轮PySide，去年夏天我做了。很棒！

提示：一些开发商至今未能支撑轮格式，仅仅是因为他们忘记更换distutils的setuptools。通常，通过替换中的单个单词很容易转换此类软件包setup.py。

点击查看英文原文

As an addition to fuzzyman’s reply:

pip won’t install binary packages and isn’t well tested on Windows.

As Windows doesn’t come with a compiler by default pip often can’t be used there. easy_install can install binary packages for Windows.

Here is a trick on Windows:

  • you can use easy_install <package> to install binary packages to avoid building a binary

  • you can use pip uninstall <package> even if you used easy_install.

This is just a work-around that works for me on windows. Actually I always use pip if no binaries are involved.

See the current pip doku: http://www.pip-installer.org/en/latest/other-tools.html#pip-compared-to-easy-install

I will ask on the mailing list what is planned for that.

Here is the latest update:

The new supported way to install binaries is going to be wheel! It is not yet in the standard, but almost. Current version is still an alpha: 1.0.0a1

https://pypi.python.org/pypi/wheel

http://wheel.readthedocs.org/en/latest/

I will test wheel by creating an OS X installer for PySide using wheel instead of eggs. Will get back and report about this.

cheers – Chris

A quick update:

The transition to wheel is almost over. Most packages are supporting wheel.

I promised to build wheels for PySide, and I did that last summer. Works great!

HINT: A few developers failed so far to support the wheel format, simply because they forget to replace distutils by setuptools. Often, it is easy to convert such packages by replacing this single word in setup.py.

回答 8

刚遇到一个我不得不easy_install代替的特殊情况pip，否则我必须直接提取源代码。

对于该软件包GitPython，in中的版本pip太旧，即0.1.7，而from中的版本easy_install是最新的，即0.3.2.rc1。

我正在使用Python 2.7.8。我不知道有关的底层机制easy_install和pip，但至少有一些包的版本可能是彼此不同的，有时easy_install是一个较新的版本。

easy_install GitPython
点击查看英文原文

Just met one special case that I had to use easy_install instead of pip, or I have to pull the source codes directly.

For the package GitPython, the version in pip is too old, which is 0.1.7, while the one from easy_install is the latest which is 0.3.2.rc1.

I’m using Python 2.7.8. I’m not sure about the underlay mechanism of easy_install and pip, but at least the versions of some packages may be different from each other, and sometimes easy_install is the one with newer version.

easy_install GitPython
知识问答

python setup.py卸载

问题：python setup.py卸载

我已经使用安装了python软件包python setup.py install。

如何卸载？

点击查看英文原文

I have installed a python package with python setup.py install.

How do I uninstall it?

回答 0

注意：避免python setup.py install使用pip install .

您需要手动删除所有文件，还需要撤消安装过程中手动执行的任何其他操作。

如果您不知道所有文件的列表，则可以使用--record选件重新安装它，然后查看生成的列表。

要记录已安装文件的列表，可以使用：

python setup.py install --record files.txt

想要卸载后，可以使用xargs进行删除：

xargs rm -rf < files.txt

或者，如果您正在运行Windows，请使用Powershell： 

Get-Content files.txt | ForEach-Object {Remove-Item $_ -Recurse -Force}

然后也删除包含的目录，例如/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/my_module-0.1.egg/on macOS。它没有文件，但是Python仍将导入一个空模块：

>>> import my_module
>>> my_module.__file__
None

删除后，Python将显示：

>>> import my_module
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'my_module'
点击查看英文原文

Note: Avoid using python setup.py install use pip install .

You need to remove all files manually, and also undo any other stuff that installation did manually.

If you don’t know the list of all files, you can reinstall it with the --record option, and take a look at the list this produces.

To record a list of installed files, you can use:

python setup.py install --record files.txt

Once you want to uninstall you can use xargs to do the removal:

xargs rm -rf < files.txt

Or if you’re running Windows, use Powershell: 

Get-Content files.txt | ForEach-Object {Remove-Item $_ -Recurse -Force}

Then delete also the containing directory, e.g. /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/my_module-0.1.egg/ on macOS. It has no files, but Python will still import an empty module:

>>> import my_module
>>> my_module.__file__
None

Once deleted, Python shows:

>>> import my_module
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'my_module'

回答 1

对我来说，以下主要工作方式：

已安装点子，例如：

$ easy_install pip

从pip的角度检查已安装的软件包的名称：

$ pip freeze

这将列出您已经安装（并且被pip检测到）的所有软件包的名称。该名称可能会很长，然后仅使用和之后显示的程序包的名称#egg=。在大多数情况下，您也可以忽略版本部分（无论是后面的==还是-）。

然后卸载该软件包：

$ pip uninstall package.name.you.have.found

如果它要求您确认删除软件包，那么您很幸运，它将被删除。

pip应检测所有由pip安装的软件包。它还应检测通过easy_install或setup.py安装的大多数软件包，但这在极少数情况下可能会失败。

这是来自本地测试的真实示例，带有ttr.rdstmc在Windows上命名的软件包。

$ pip freeze |grep ttr
ttr.aws.s3==0.1.1dev
ttr.aws.utils.s3==0.3.0
ttr.utcutils==0.1.1dev

$ python setup.py develop
.....
.....
Finished processing dependencies for ttr.rdstmc==0.0.1dev

$ pip freeze |grep ttr
ttr.aws.s3==0.1.1dev
ttr.aws.utils.s3==0.3.0
-e hg+https://vlcinsky@bitbucket.org/vlcinsky/ttr.rdstmc@d61a9922920c508862602f7f39e496f7b99315f0#egg=ttr.rdstmc-dev
ttr.utcutils==0.1.1dev

$ pip uninstall ttr.rdstmc
Uninstalling ttr.rdstmc:
  c:\python27\lib\site-packages\ttr.rdstmc.egg-link
Proceed (y/n)? y
  Successfully uninstalled ttr.rdstmc

$ pip freeze |grep ttr
ttr.aws.s3==0.1.1dev
ttr.aws.utils.s3==0.3.0
ttr.utcutils==0.1.1dev

编辑2015-05-20

上面写的所有内容仍然适用，无论如何，现在有一些小的修改。

在python 2.7.9和python 3.4中安装pip

最新的python版本附带了一个软件包ensurepip，即使离线也可以安装pip：

$ python -m surepip-升级

在某些系统（例如Debian Jessie）上，此功能不可用（以防止破坏系统python安装）。

使用grep或find

上面的示例假定您已grep安装。我（当时我的计算机上装有MS Windows）安装了一套Linux实用程序（包括grep）。或者，使用本机MS Windows find或简单地忽略该过滤，并在更长的检测到的python软件包列表中找到名称。

点击查看英文原文

For me, the following mostly works:

have pip installed, e.g.:

$ easy_install pip

Check, how is your installed package named from pip point of view:

$ pip freeze

This shall list names of all packages, you have installed (and which were detected by pip). The name can be sometime long, then use just the name of the package being shown at the and after #egg=. You can also in most cases ignore the version part (whatever follows == or -).

Then uninstall the package:

$ pip uninstall package.name.you.have.found

If it asks for confirmation about removing the package, then you are lucky guy and it will be removed.

pip shall detect all packages, which were installed by pip. It shall also detect most of the packages installed via easy_install or setup.py, but this may in some rare cases fail.

Here is real sample from my local test with package named ttr.rdstmc on MS Windows.

$ pip freeze |grep ttr
ttr.aws.s3==0.1.1dev
ttr.aws.utils.s3==0.3.0
ttr.utcutils==0.1.1dev

$ python setup.py develop
.....
.....
Finished processing dependencies for ttr.rdstmc==0.0.1dev

$ pip freeze |grep ttr
ttr.aws.s3==0.1.1dev
ttr.aws.utils.s3==0.3.0
-e hg+https://vlcinsky@bitbucket.org/vlcinsky/ttr.rdstmc@d61a9922920c508862602f7f39e496f7b99315f0#egg=ttr.rdstmc-dev
ttr.utcutils==0.1.1dev

$ pip uninstall ttr.rdstmc
Uninstalling ttr.rdstmc:
  c:\python27\lib\site-packages\ttr.rdstmc.egg-link
Proceed (y/n)? y
  Successfully uninstalled ttr.rdstmc

$ pip freeze |grep ttr
ttr.aws.s3==0.1.1dev
ttr.aws.utils.s3==0.3.0
ttr.utcutils==0.1.1dev

Edit 2015-05-20

All what is written above still applies, anyway, there are small modifications available now.

Install pip in python 2.7.9 and python 3.4

Recent python versions come with a package ensurepip allowing to install pip even when being offline:

$ python -m ensurepip –upgrade

On some systems (like Debian Jessie) this is not available (to prevent breaking system python installation).

Using grep or find

Examples above assume, you have grep installed. I had (at the time I had MS Windows on my machine) installed set of linux utilities (incl. grep). Alternatively, use native MS Windows find or simply ignore that filtering and find the name in a bit longer list of detected python packages.

回答 2

第一个答案有问题：

  • 在Mac上无法使用。
  • 如果安装的文件包含空格或其他特殊字符，该xargs命令将失败，并删除与各个单词匹配的所有文件/目录。
  • 在-r中rm -rf是不必要的，在最坏的情况可能会删除你不想要的东西。

相反，对于类Unix：

sudo python setup.py install --record files.txt
# inspect files.txt to make sure it looks ok. Then:
tr '\n' '\0' < files.txt | xargs -0 sudo rm -f --

对于Windows：

python setup.py bdist_wininst
dist/foo-1.0.win32.exe

卸载setup.py安装还有一些无法解决的问题，在典型情况下不会打扰您。有关更完整的答案，请参见以下Wiki页面：

https://ofswiki.org/wiki/Uninstalling_setup.py_install

点击查看英文原文

The #1 answer has problems:

  • Won’t work on mac.
  • If a file is installed which includes spaces or other special characters, the xargs command will fail, and delete any files/directories which matched the individual words.
  • the -r in rm -rf is unnecessary and at worst could delete things you don’t want to.

Instead, for unix-like:

sudo python setup.py install --record files.txt
# inspect files.txt to make sure it looks ok. Then:
tr '\n' '\0' < files.txt | xargs -0 sudo rm -f --

And for windows:

python setup.py bdist_wininst
dist/foo-1.0.win32.exe

There are also unsolvable problems with uninstalling setup.py install which won’t bother you in a typical case. For a more complete answer, see this wiki page:

https://ofswiki.org/wiki/Uninstalling_setup.py_install

回答 3

首先记录您已安装的文件。即使您先前已经运行过，也可以重复此命令setup.py install：

python setup.py install --record files.txt

要卸载时，您可以：

sudo rm $(cat files.txt)

之所以可行，是因为rm命令使用空格分隔的文件列表来删除，并且您的安装记录就是这样的列表。

点击查看英文原文

First record the files you have installed. You can repeat this command, even if you have previously run setup.py install:

python setup.py install --record files.txt

When you want to uninstall you can just:

sudo rm $(cat files.txt)

This works because the rm command takes a whitespace-seperated list of files to delete and your installation record is just such a list.

回答 4

现在，python让您可以选择在安装pip过程中进行安装（我在Windows上，至少python在Windows上可以！）。考虑到您已选择pip在安装python时进行安装（实际上是默认设置，因此不必选择），pip已经为您安装了。然后，pip在命令提示符下键入，您应该会看到一个帮助。您可以在此处找到必要的使用说明。例如，pip list显示已安装软件包的列表。您可以使用

pip uninstall package_name

卸载不再需要的任何软件包。在此处阅读更多信息（pip文档）。

点击查看英文原文

Now python gives you the choice to install pip during the installation (I am on Windows, and at least python does so for Windows!). Considering you had chosen to install pip during installation of python (you don’t actually have to choose because it is default), pip is already installed for you. Then, type in pip in command prompt, you should see a help come up. You can find necessary usage instructions there. E.g. pip list shows you the list of installed packages. You can use

pip uninstall package_name

to uninstall any package that you don’t want anymore. Read more here (pip documentation).

回答 5

懒惰的方式：只需从Windows安装菜单（如果使用Windows）或从rpm命令卸载，前提是您在创建分发程序包后首先重新安装它。

例如，

python setup.py bdist_wininst
dist/foo-1.0.win32.exe

（“ foo”当然是示例）。

点击查看英文原文

The lazy way: simply uninstall from the Windows installation menu (if you’re using Windows), or from the rpm command, provided you first re-install it after creating a distribution package.

For example,

python setup.py bdist_wininst
dist/foo-1.0.win32.exe

(“foo” being an example of course).

回答 6

转到python软件包目录并删除.egg文件，例如：在python 2.5（ubuntu）中：/usr/lib/python2.5/site-packages/

在python 2.6（ubuntu）中：/usr/local/lib/python2.6/dist-packages/

点击查看英文原文

Go to your python package directory and remove your .egg file, e.g.: In python 2.5(ubuntu): /usr/lib/python2.5/site-packages/

In python 2.6(ubuntu): /usr/local/lib/python2.6/dist-packages/

回答 7

不能完全回答问题，但每天都能对我有所帮助：

安装您的软件包

pip install .

这会将包装放入$HOME/.local。卸载

pip uninstall <package_name>
点击查看英文原文

Not exactly answering the question, but something that helps me every day:

Install your packages with

pip install .

This puts the package in $HOME/.local. Uninstall with

pip uninstall <package_name>

回答 8

可能您可以这样做：

1）获取python版本-

[linux machine]# python
Python 2.4.3 (#1, Jun 18 2012, 14:38:55)

->上面的命令为您提供了当前的python版本2.4.3

2）获取python的安装目录-

[linux machine]# whereis python
python: /usr/bin/python /usr/bin/python2.4 /usr/lib/python2.4 /usr/local/bin/python2.5 /usr/include/python2.4 /usr/share/man/man1/python.1.gz

->从上面的命令中，您可以获得安装目录-/ usr/lib/python2.4/site – packages

3）从这里您可以删除软件包和python egg文件

[linux machine]# cd /usr/lib/python2.4/site-packages
[linux machine]# rm -rf paramiko-1.12.0-py2.4.egg paramiko-1.7.7.1-py2.4.egg paramiko-1.9.0-py2.4.egg

这对我有用。而且我能够卸载困扰我的软件包:)

点击查看英文原文

Probably you can do this as an alternative :-

1) Get the python version –

[linux machine]# python
Python 2.4.3 (#1, Jun 18 2012, 14:38:55)

-> The above command gives you the current python Version which is 2.4.3

2) Get the installation directory of python –

[linux machine]# whereis python
python: /usr/bin/python /usr/bin/python2.4 /usr/lib/python2.4 /usr/local/bin/python2.5 /usr/include/python2.4 /usr/share/man/man1/python.1.gz

-> From above command you can get the installation directory which is – /usr/lib/python2.4/site-packages

3) From here you can remove the packages and python egg files

[linux machine]# cd /usr/lib/python2.4/site-packages
[linux machine]# rm -rf paramiko-1.12.0-py2.4.egg paramiko-1.7.7.1-py2.4.egg paramiko-1.9.0-py2.4.egg

This worked for me.. And i was able to uninstall package which was troubling me :)

回答 9

我认为您可以打开setup.py，找到软件包名称，然后要求pip卸载它。

假设名称在“ METADATA”变量中可用：

pip uninstall $(python -c "from setup import METADATA; print METADATA['name']")
点击查看英文原文

I think you can open the setup.py, locate the package name, and then ask pip to uninstall it.

Assuming the name is available in a ‘METADATA’ variable:

pip uninstall $(python -c "from setup import METADATA; print METADATA['name']")

回答 10

扩展一下Martin所说的内容，记录安装输出和一些bash脚本就可以很好地解决问题。这是我的工作

for i in $(less install.record);
sudo rm $i;
done;

和presto。已卸载。

点击查看英文原文

Extending on what Martin said, recording the install output and a little bash scripting does the trick quite nicely. Here’s what I do…

for i in $(less install.record);
sudo rm $i;
done;

And presto. Uninstalled.

回答 11

如果在重新安装软件包后仍有一些文件应删除，请确保该文件夹build也已删除。因此，假设这pkg是您要删除的软件包：

rm -r $(python3 -c "import pkg; print(pkg.__path__[0] + '*' )") 
rm -rf build

以上为python3计算并删除了软件包及其* .egg-info文件

点击查看英文原文

If you still have files that are supposed to be deleted after re-installing a package, make sure the folder build is also deleted. Therefore, assuming that pkg is the package you want to delete:

rm -r $(python3 -c "import pkg; print(pkg.__path__[0] + '*' )") 
rm -rf build

Obove work out for python3 and delete the package and its *.egg-info file

回答 12

在{virtualenv}/lib/python2.7/site-packages/（如果未使用virtualenv，则为{system_dir}/lib/python2.7/dist-packages/）

  • 删除鸡蛋文件（例如distribute-0.6.34-py2.7.egg）
  • 如果文件中有任何内容easy-install.pth，请删除相应的行（它应该是源目录或egg文件的路径）。
点击查看英文原文

At {virtualenv}/lib/python2.7/site-packages/ (if not using virtualenv then {system_dir}/lib/python2.7/dist-packages/)

  • Remove the egg file (e.g. distribute-0.6.34-py2.7.egg)
  • If there is any from file easy-install.pth, remove the corresponding line (it should be a path to the source directory or of an egg file).

回答 13

我过去曾经在全局环境中偶然运行过“ python setup.py install”，并且卸载时遇到很多困难。这些解决方案没有帮助。“ pip卸载”不适用于“无法卸载’splunk-appinspect’。找不到要卸载的文件。” “ sudo pip卸载”不起作用“无法卸载要求splunk-appinspect，未安装”。我尝试卸载pip，删除pip缓存，在硬盘上搜索该软件包等，…

“ pip show”最终将我引向解决方案，“ Location：”指向目录，并且重命名该目录导致打包的内容从pip列表中删除。我重命名了目录，但它没有重新出现在pip的列表中，现在我可以在virtualenv中重新安装我的软件包了。

点击查看英文原文

I had run “python setup.py install” at some point in the past accidentally in my global environment, and had much difficulty uninstalling. These solutions didn’t help. “pip uninstall ” didn’t work with “Can’t uninstall ‘splunk-appinspect’. No files were found to uninstall.” “sudo pip uninstall ” didn’t work “Cannot uninstall requirement splunk-appinspect, not installed”. I tried uninstalling pip, deleting the pip cache, searching my hard drive for the package, etc…

“pip show ” eventually led me to the solution, the “Location:” was pointing to a directory, and renaming that directory caused the packaged to be removed from pip’s list. I renamed the directory back, and it didn’t reappear in pip’s list, and now I can reinstall my package in a virtualenv.

回答 14

我python setup.py install在PyCharm中运行了一次，它将所有软件包安装到conda基本环境中。以后，当我要删除所有这些程序包时，将pip uninstall无法正常工作。我不得不从/anaconda3/lib/python3.7/site-packages中手动删除它们:(

因此，我看不出他们为什么使用setup.py而不是编写requirements.txt文件的原因。需求文件可用于在虚拟环境中安装软件包，并且不会与系统python软件包混淆。

点击查看英文原文

I had run python setup.py install once in my PyCharm, it installs all the packages into my conda base environment. Later when I want to remove all these packages, pip uninstall does not work. I had to delete them from /anaconda3/lib/python3.7/site-packages manually :(

So I don’t see the reason why they use setup.py instead of writing requirements.txt file. The requirement file can be used to install packages in virtual environment and won’t mess with system python packages.

回答 15

最好使用bash读取命令来删除相关文件，如下所示：

sudo python setup.py install --record files.txt
sudo bash -c "cat files.txt | xargs rm -rf"
点击查看英文原文

It might be better to remove related files by using bash to read commands, like the following:

sudo python setup.py install --record files.txt
sudo bash -c "cat files.txt | xargs rm -rf"
github

Youtube-dl-gui-用wxPython编写的流行的youtube-dl的跨平台前端GUI

一款流行的跨平台前端GUIyoutube-dl用wxPython编写的媒体下载器。Supported sites

屏幕截图

要求

下载次数

安装

从源安装

  1. 下载并解压缩源代码
  2. 将目录更改为youtube-dl-gui-0.4
  3. 跑python setup.py install

安装PyPi

  1. 跑pip install youtube-dlg

安装Windows Installer

  1. 下载并解压缩Windows Installer
  2. 运行setup.exe文件

贡献

作者

看见AUTHORS文件

许可证

这个Public Domain License

常见问题解答

看见FAQs文件

谢谢

感谢为这个项目做出贡献的每一个人，感谢@philipzae用于设计新的UI布局