| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Sat, Oct 11, 2014 at 04:23:37PM -0000, Jason R. Coombs wrote [1]:
> I suggest implementing the functionality as a separate method with a
> docstring explaining the purpose.
so that's what we have here. The docstring is adapted from the
cbd4f603 (egg_info: Search egg-base for files to add to the manifest,
2014-10-16) commit message.
It's a lot of docs for a single command (although there is a newsted
list comprehension), so I'm fine if you drop this commit before
merging. The motivation behind the lines would still be available in
the version control history:
$ hg blame -c setuptools/command/egg_info.py | grep -A1 ei_cmd.egg_base
cbd4f6038604: if ei_cmd.egg_base != os.curdir:
cbd4f6038604: self.filelist.allfiles.extend([
cbd4f6038604: os.path.join(ei_cmd.egg_base, path)
cbd4f6038604: for path in distutils.filelist.findall(ei_cmd.egg_base)])
80108b046cb6: self.filelist.include_pattern("*", prefix=ei_cmd.egg_info)
$ hg log -vr cbd4f6038604
changeset: 3163:cbd4f6038604
...
description:
egg_info: Search egg-base for files to add to the manifest
Before this commit, this:
$ mkdir -p /tmp/xyz/{home,lib,scripts,data,egg}
$ cat >/tmp/xyz/home/.pydistutils.cfg <<EOF
...
[1]: https://bitbucket.org/pypa/setuptools/pull-request/85/egg_info-search-egg-base-for-files-to-add/diff#comment-3418032
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this commit, this:
$ mkdir -p /tmp/xyz/{home,lib,scripts,data,egg}
$ cat >/tmp/xyz/home/.pydistutils.cfg <<EOF
> [egg_info]
> egg-base = /tmp/xyz/egg
> EOF
$ export PYTHONPATH=/tmp/xyz/lib
$ export HOME=/tmp/xyz/home
$ setup.py install --home=/tmp/xyz/home --install-lib=/tmp/xyz/lib \
> --install-scripts=/tmp/xyz/scripts --install-data=/tmp/xyz/data
drops a lot of metadata, installing only SOURCES.txt and zip-safe
under EGG-INFO. The problem is that the metadata files are written to
egg-base, but egg-base is not searched when creating the manifest
because it's outside of the current directory. Work around this by
explicitly searching egg-base with distutils.filelist.findall (which
is really the version monkeypatched in by setuptools/__init__.py).
Since findall records relative paths, prefix the returned paths with
egg-base, so the include_pattern looking for the absolute
ei_cmd.egg_info will match them.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
.hgtags
CHANGES.txt
ez_setup.py
setuptools.egg-info/requires.txt
setuptools/version.py
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | |
| |
| |
| |
| | |
--HG--
extra : amend_source : d7b3c001b4db616a67793dcc57d5c13e3828ad3a
|
| | |
| |
| |
| |
| |
| |
| | |
included in the list of modified files.
--HG--
extra : rebase_source : 8bad8bf37ef1fdc59b4c1ba21fcff43d25f9b2be
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
Syntax error introduced in be37eff86c761a399c1ec98b0e5eeed9a90c9cd7
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
single_version_externally_managed
|
| | | |
| | |
| | |
| | | |
container.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | | |
Fix exclude list on python 3.2+
|
| | |\ \
| | |/ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I shall `hg status` before submitting PRs.
I shall `hg status` before submitting PRs.
I shall `hg status` before submitting PRs.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
imp.get_tag() is only available on 3.2+. Since 2<x<3.2 are EOL we shall
not worry.
We could implement a local get_tag(), but the point is moot: this
compilation tactic with __pycache__ subdirs and versioned import files
is new to python 3.x, so hasattr() is sufficient.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should fix the problem in Bitbucket issue #100. It gives the same behavior
for inclusion of default files (README*, etc.) on Windows as Linux.
BACKWARDS INCOMPATABILITY:
This may result in a backwards incompatible change for users on a
case insensitive file system. If they were relying on some files getting
included in their distribution due to setuptools defaults, and their files do not
have the same case as the files being looked for in setuptools, those files
will no longer be included in the package.
For example, if a package had a file:
readme.rst
Previous to this commit, that file would have been included in the distribution
as:
README.rst
But it will now no longer be included at all. To get the file included in
the package, it can be added to the package's MANIFEST.in file:
include readme.rst
Files affected by this change will have a case variant of the files or
patterns listed below:
README
README.txt
README.rst
setup.py (or whatever your setuptools script is named)
setup.cfg
test/test*.py
|
| | |/
|/|
| |
| | |
Syntax was invalid.
|
| | |
| |
| |
| | |
like it was done for requirements and entry_points
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
--HG--
extra : amend_source : 9576c3d20e8d3bcb3b951cd2f588e782f885ebe6
|
| | |
| |
| |
| |
| |
| |
| |
| | |
such sub directories.
--HG--
branch : develop
extra : rebase_source : 2b3326fe668e880b351b0d5f388472239d915d58
|
| | |
| |
| |
| |
| |
| | |
--HG--
branch : develop
extra : rebase_source : 571dac8142fc43b54bcd0302598766b0bb9e13ff
|
| | |
| |
| |
| |
| | |
--HG--
extra : amend_source : fa41c3fb787b667f703f67a52aed7a2958e615b4
|