| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
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
|
| | | |
|
| | |
| |
| |
| | |
67bdf3a726962 where only the last dat would be written.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
--HG--
extra : rebase_source : beb6c57dfd500432304518b9d313d1a98e2614b9
|
| | | |
| | |
| | |
| | |
| | | |
--HG--
extra : rebase_source : 04b4807ccc7bf95d87797716f5d3488d420fa692
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
PyPy's zipimport._zip_directory_cache implementation does not support direct
item assignment, thus breaking our attempts at silently updating the cached zip
archive directory information behind the scene. As a workaround, when using
PyPy, we fall back to simply clearing the stale cached information.
--HG--
extra : amend_source : 991e30244754d8fac042da56ac4cf0ad1a0f50d5
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is an extra safety measure to avoid someone holding a reference to this
cached data and using its content even after we know that the underlying zip
archive has been removed and possibly even replaced.
Change suggested by PJ Eby (pje on BitBucket) in a setuptools pull request #51
comment:
https://bitbucket.org/pypa/setuptools/pull-request/51/diff#comment-2018183
--HG--
extra : rebase_source : 6de2309bc7446647749cfe78ab00e0230a07f92f
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
_update_zipimporter_cache() extracted from _uncache() &
_replace_zip_directory_cache_data().
Code cleanup done in preparation for adding a bit more detailed cache item
clearing logic, so that would not require adding a separate function with yet
more code duplication.
--HG--
extra : rebase_source : e2e956e042c7cbfabe2c31ecc58a4f76c91f40aa
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Extracted code for collecting a list of zipimporter cache entries related to a
given path into _collect_zipimporter_cache_entries().
--HG--
extra : rebase_source : 54ab881d794f95467e811511433a2cd31595339e
|
| | | |
| | |
| | |
| | |
| | | |
--HG--
extra : rebase_source : c8c77d96880275e34c1580991c2d70486b6d0e00
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
pypy uses a custom zipimport._zip_directory_cache implementation class that
does not support the complete dict interface, e.g. it does not support the
dict.pop() method.
For more detailed information see the following links:
https://bitbucket.org/pypa/setuptools/issue/202/more-robust-zipimporter-cache-invalidation#comment-10495960
https://bitbucket.org/pypy/pypy/src/dd07756a34a41f674c0cacfbc8ae1d4cc9ea2ae4/pypy/module/zipimport/interp_zipimport.py#cl-99
--HG--
extra : rebase_source : 95cff7946455f0a4422d97eecab11164a9ddef10
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Although the original problematic use case when we are replacing a zipped egg
distribution with another zipped egg distribution is now cleanly handled by
fixing all existing zipimport.zipimporter loaders, this fix is still valid for
cases when replacing a distribution with a non-zipped egg folder.
--HG--
extra : source : efd6a8b82bafdbcfad1971b7e0f470e19191be1a
|