| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Original patch by Julien Courteau and Pierre Paul Lefebvre.
|
| |
|
|
|
|
|
|
| |
These files are created by some NFS clients a file is edited and removed
concurrently (see added link in doc for more info). If such a file is
removed between distutils calls listdir and copy, it will get confused.
Other special files are ignored in sdist (namely VCS directories), but
this has to be filtered out earlier.
|
| | |
|
| | |
|
| |
|
|
| |
Patch by Ralf Schmitt.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These regex changes fix a number of issues for distutils on Windows:
- #6884: impossible to include a file starting with 'build'
- #9691 and #14004: sdist includes too many files
- #13193: test_filelist failures
This commit replaces the incorrect changes done in 0a94e2f807c7 and
90b30d62caf2 to fix #13193; we were too eager to fix the test failures
and I did not study the code enough before greenlighting patches. This
time we have unit tests from the problems reported by users to be sure
we have the right fix.
Thanks to Nadeem Vawda for his help.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
Bug reported by Hartmut Goebel and patch contributed by Carl Robben.
Carl tested the fix and we have a buildbot with rpm installed, so I’m
committing even though I could not run this test (but I do understand
the changed code :)
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
| |
- Actually check the contents of the file created by bdist_dumb.
- Don’t use “RECORD” as filename for non-PEP 376 record file
- Don’t start method name with “_test”, it smells like a disabled test
method instead of an helper method
- Fix some idioms (assertIn, addCleanup)
|
| |
|
|
| |
manifest
|
| |
|
|
| |
Patch by Justin Love.
|
| | |
|
| |
|
|
| |
Patch by Jeff Ramnani. Tested with -B, -O and -OO.
|
| |
|
|
| |
Patch by Hallvard B Furuseth.
|
| | |
|
| |
|
|
|
| |
I have tests to add in this file and it’s always nice to start from a
clean base.
|
| |
|
|
|
| |
sdist used to crash with a full traceback dump instead of printing a
nice warning with the faulty line number.
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- First, support.fixup_build_ext (already used to set proper
library_dirs value under Unix shared builds) gains the ability to
correctly set the debug attribute under Windows debug builds.
- Second, the filename for the extension module gets a _d suffix under
debug builds.
- Third, the test code properly puts our customized build_ext object
into an internal dictionary to make sure that the install command will
later use our object instead of re-creating one. That’s the downside
of using low-level APIs in our test code: we have to manually push
knobs and turn handles that would otherwise be handled behind the
scenes.
Thanks to Nadeem for the testing.
|
| |
|
|
| |
Patch by Jeremy Kloth.
|
| | |
|
| |
|
|
| |
I need this to fix the failing test_install.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
I made a note a month ago that install --record wrote incorrect entries
for extension modules (I think the problem was that the first character
of the file was stripped), so I’m now adding a test to try to reproduce
that in the current versions.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
I need to copy this file in another test too, so I moved the support
code to distutils.tests.support and improved it:
- don’t skip when run from the Lib/distutils/tests directory
- use proper skip machinery instead of custom print/return/test suite
fiddling.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The changed behavior of sdist in 3.1 broke packaging for projects that
wanted to use a manually-maintained MANIFEST file (instead of having a
MANIFEST.in template and letting distutils generate the MANIFEST).
The fixes that were committed for #8688 (76643c286b9f by Tarek and
d54da9248ed9 by me) did not fix all issues exposed in the bug report,
and also added one problem: the MANIFEST file format gained comments,
but the read_manifest method was not updated to handle (i.e. ignore)
them. This changeset should fix everything; the tests have been
expanded and I successfully tested the 2.7 version with Mercurial, which
suffered from this regression.
I have grouped the versionchanged directives for these bugs in one place
and added micro version numbers to help users know the quirks of the
exact version they’re using.
Initial report, thorough diagnosis and patch by John Dennis, further
work on the patch by Stephen Thorne, and a few edits and additions by
me.
|
| |
|
|
| |
longer applicable in hg. Patch Contributed by Neil Muller.
|
| |
|
|
| |
test_build_ext.
|
| |
|
|
|
| |
test_build_ext of test_distutils is no longer silently skipped when
run outside of a build directory.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The tests now pass all combinations of -O/-OO and -B. See also #7071
and #6292 for previous variations on the same theme.
test_versionpredicate needs a skip when sys.flags.optimize is true, but
I don’t know how to make that work with a DocTestSuite.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
in shell.
Without this patch python will fail to start properly when the environment
variable MACOSX_DEPLOYMENT_TARGET is set on MacOSX and has a value that is
not compatible with the value during Python's build. This is caused by code
in sysconfig that was only meant to be used in disutils.
|
| |\ \
| |/ |
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| |\ \
| |/ |
|
