blocks|key|773798|text|include_package_data=True为我工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|773799|如果您使用git，请记住在install_requires中包含setuptools-git。比拥有Manifest或者在package_data中包含所有路径要简单得多(在我的例子中，它是一个django应用程序，包含了所有类型的静态)|773800|(粘贴了我的评论，正如k3-rnc提到的那样，它实际上是有帮助的)|773801|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/7522250/how-to-include-package-data-with-setuptools-distribute#comment56156410_7522250^0|0|P|0|D|G|W|E|1E|8|1P|C|0|B|6|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|J|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

<code>include_package_data=True</code> worked for me.

If you use git, remember to include <code>setuptools-git</code> in <code>install_requires</code>. Far less boring than having a <code>Manifest</code> or including all path in <code>package_data</code> ( in my case it's a django app with all kind of statics )

( pasted the comment I made, as <a href="https://stackoverflow.com/questions/7522250/how-to-include-package-data-with-setuptools-distribute#comment56156410_7522250">k3-rnc</a> mentioned it's actually helpful as is )

blocks|key|557419|text|古老的问题，然而..。python的包管理确实有很多不足之处。因此，我使用pip在本地将其安装到指定的目录，并惊讶地发现package_data和data_files路径都不起作用。我并不热衷于将另一个文件添加到存储库，因此我最终使用了安装和数据选项--+data_files+-+setup.py；类似如下|type|unstyled|depth|inlineStyleRanges|entityRanges|data|557420|pip+install+.+--install-option="--install-data=$PWD/package"+-t+package++|code-block|syntax|javascript|557421|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Ancient question and yet... package management of python really leaves a lot to be desired. So I had the use case of installing using pip locally to a specified directory and was surprised both package_data and data_files paths did not work out. I was not keen on adding yet another file to the repo so I ended up leveraging data_files and setup.py option --install-data; something like this

<pre><code>pip install . --install-option="--install-data=$PWD/package" -t package 
</code></pre>

blocks|key|773767|text|将包含包数据的文件夹移动到模块文件夹为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|773768|请看这个问题：MANIFEST.in+ignored+on+"python+setup.py+install"+-+no+data+files+installed?|offset|length|773769|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3596979/manifest-in-ignored-on-python-setup-py-install-no-data-files-installed^0|0|7|23|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Moving the folder containing the package data into to module folder solved the problem for me.

See this question: <a href="https://stackoverflow.com/questions/3596979/manifest-in-ignored-on-python-setup-py-install-no-data-files-installed">MANIFEST.in ignored on &quot;python setup.py install&quot; - no data files installed?</a>

blocks|key|557473|text|使用setup.cfg+(setuptools≥30.3.0)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|557474|从setuptools+30.3.0+(发布于2016-12-08)开始，您可以保持setup.py非常小，并将配置移动到setup.cfg文件中。使用这种方法，您可以将包数据放在[options.package_data]部分中：|offset|length|style|CODE|557475|[options.package_data]
*+=+*.txt,+*.rst
hello+=+*.msg|code-block|syntax|javascript|557476|在这种情况下，您的setup.py可以简短为：|557477|from+setuptools+import+setup
setup()|557478|有关详细信息，请参阅configuring+setup+using+setup.cfg+files。|557479|有some+talk+of+deprecating+setup.cfg支持PEP+518中提出的pyproject.toml，但这在2020-02-21仍是临时的。|557480|entityMap|0|LINK|mutability|MUTABLE|url|https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files|1|https://stackoverflow.com/a/56523197/974555|2|https://www.python.org/dev/peps/pep-0518/^0|0|16|8|1P|9|2I|M|0|0|9|8|0|0|A|13|0|0|Q|9|1C|E|1|Y|1|11|7|2|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]|$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1E|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|1I|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|S|3|T|5|6|7|1N|8|@$D|1O|E|1P|F|G]|$D|1Q|E|1R|F|G]]|9|@$D|1S|E|1T|1|1U]|$D|1V|E|1W|1|1X]]|A|$]]|$1|U|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]|14|$5|X|Y|Z|A|$10|15]]]]

<h2>Using setup.cfg (setuptools ≥ 30.3.0)</h2>

Starting with setuptools 30.3.0 (released 2016-12-08), you can keep your <code>setup.py</code> very small and move the configuration to a <code>setup.cfg</code> file. With this approach, you could put your package data in an <code>[options.package_data]</code> section:

<pre><code>[options.package_data]
* = *.txt, *.rst
hello = *.msg
</code></pre>

In this case, your <code>setup.py</code> can be as short as:

<pre class="lang-py prettyprint-override"><code>from setuptools import setup
setup()
</code></pre>

For more information, see <a href="https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files" rel="nofollow noreferrer">configuring setup using setup.cfg files</a>.

There is <a href="https://stackoverflow.com/a/56523197/974555">some talk of deprecating <code>setup.cfg</code></a> in favour of <code>pyproject.toml</code> as proposed in <a href="https://www.python.org/dev/peps/pep-0518/" rel="nofollow noreferrer">PEP 518</a>, but this is still provisional as of 2020-02-21.

blocks|key|557504|text|只需删除这一行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|557505|include_package_data=True,|code-block|syntax|javascript|557506|从您的设置脚本，它将工作得很好。(刚才使用最新的setuptools进行了测试。)|557507|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Just remove the line:

<pre><code>include_package_data=True,
</code></pre>

from your setup script, and it will work fine. (Tested just now with latest setuptools.)

blocks|key|557554|text|对于像这样的目录结构：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|557555|foo/
├──+foo
│  +├──+__init__.py
│  +├──+a.py
│  +└──+data.txt
└──+setup.py|code-block|syntax|javascript|557556|和setup.py|offset|length|style|CODE|557557|#!/usr/bin/env+python
#+-*-+coding:+utf-8+-*-

from+setuptools+import+setup


NAME+=+'foo'
DESCRIPTION+=+'Test+library+to+check+how+setuptools+works'
URL+=+'https://none.com'
EMAIL+=+'gzorp@bzorp.com'
AUTHOR+=+'KT'
REQUIRES_PYTHON+=+'>=3.6.0'

setup(
++++name=NAME,
++++version='0.0.0',
++++description=DESCRIPTION,
++++author=AUTHOR,
++++author_email=EMAIL,
++++python_requires=REQUIRES_PYTHON,
++++url=URL,
++++license='MIT',
++++classifiers=[
++++++++'Programming+Language+::+Python',
++++++++'Programming+Language+::+Python+::+3',
++++++++'Programming+Language+::+Python+::+3.6',
++++],
++++packages=['foo'],
++++package_data={'foo':+['data.txt']},
++++include_package_data=True,
++++install_requires=[],
++++extras_require={},
++++cmdclass={},
)|557558|python+setup.py+bdist_wheel起作用了。|557559|entityMap^0|0|0|1|8|0|0|0|R|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

For a directory structure like:
<pre><code>foo/
├── foo
│   ├── __init__.py
│   ├── a.py
│   └── data.txt
└── setup.py
</code></pre>
and <code>setup.py</code>
<pre><code>#!/usr/bin/env python
# -*- coding: utf-8 -*-

from setuptools import setup


NAME = 'foo'
DESCRIPTION = 'Test library to check how setuptools works'
URL = 'https://none.com'
EMAIL = 'gzorp@bzorp.com'
AUTHOR = 'KT'
REQUIRES_PYTHON = '&gt;=3.6.0'

setup(
 name=NAME,
 version='0.0.0',
 description=DESCRIPTION,
 author=AUTHOR,
 author_email=EMAIL,
 python_requires=REQUIRES_PYTHON,
 url=URL,
 license='MIT',
 classifiers=[
 'Programming Language :: Python',
 'Programming Language :: Python :: 3',
 'Programming Language :: Python :: 3.6',
 ],
 packages=['foo'],
 package_data={'foo': ['data.txt']},
 include_package_data=True,
 install_requires=[],
 extras_require={},
 cmdclass={},
)
</code></pre>
<code>python setup.py bdist_wheel</code> works.

When using setuptools, I can not get the installer to pull in any <a href="https://pythonhosted.org/setuptools/setuptools.html#including-data-files" rel="noreferrer"><code>package_data</code></a> files. Everything I've read says that the following is the correct way to do it. Can someone please advise?
<pre><code>setup(
 name='myapp',
 packages=find_packages(),
 package_data={
 'myapp': ['data/*.txt'],
 },
 include_package_data=True,
 zip_safe=False,
 install_requires=['distribute'],
)
</code></pre>
where <code>myapp/data/</code> is the location of the data files.

How to include package data with setuptools/distutils?

Python

使用setuptools时，我无法让安装程序拉入任何文件。我读到的所有东西都告诉我，以下是正确的做法。有人能给点建议吗？setup(   name='myapp',   packages=find_packages(),   package_data={      'myapp': ['data/*.txt'],   },   include_package_data=True,   zip_sa

问如何在setuptools/distutils中包含包数据？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在setuptools/distutils中包含包数据？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在setuptools/distutils中包含包数据？
EN