| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | | |
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The contents of this attribute are an implementation detail, as
documented for #9442, so we should not parse it, to support non-CPython
VMs in the future.
Unfortunately, one use comes directly from PEP 345, so an edit will have
to be agreed before fixing the code (see comment in d2.markers).
Other remaining uses are found in d2.compiler and could be replaced by
the platform module (which also parses sys.version, but then it wouldn?t
be my fault :)
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | |\
| | |
| | |
| | |
| | | |
I broke test_mixin2to3 somehow; distutils2-default is okay and packaging too,
so I don?t see an obvious reason right now, I?ll investigate later.
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The deprecation warning emitted by RawConfigParser.readfp (used in util
and config, and from config in many places) will be annoying for
developers using distutils2 as a library; maybe we should drop 3.1
compat (people are expected to switch from 2.7 to 3.2 directly) and
switch to RawConfigParser.read_file.
One test in test_pypi_simple fails on 3.3 due to a recent change (see
#10680); I didn?t fix it because I can?t open the bug report that the
test was written for, and anyway the whole file should be rewritten to
use assertRaises. I have to leave some things for Alexis :)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This codebase is compatible with 3.1, 3.2 and 3.3. It was converted with 2to3
and a semi-automated diff/merge with packaging in 3.3 to fix some idioms.
We?ve now come full circle from 2.x to 3.x to 2.x to 3.x again :)
Starting from now, contributors can make patches for packaging (preferred, as
the stdlib?s regrtest is very useful), distutils2 or distutils-python3, and
we?ll make patches flow between versions.
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should help avoiding issues like #13170.
Because of implicit relative imports, _backport.tarfile already imported
shutil from the backports instead of the stdlib; I have inlined the only
function it needed to remove the circular dependency between these
modules.
|
| | | |
| | |
| | |
| | | |
In addition, update the create module to use logging.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This method was named reinitialize_command in distutils and accompanied
by a comment suggesting to change it to get_reinitialized_command.
Following that, I did the change for distutils2, but it proved
confusing: The Distribution object has an internal cache of command
objects, to make sure only one instance is ever used, and the name
get_reinitialized_command could suggest that the object returned was
independent of that cache, which it was not. I?m reverting the name
change to make code clearer.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I think I?ve got all of them (I?ll clean up compat after); if someone
knows a lint tool that can detect missing super calls, please let me
know.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I need this for some tests, and it makes code clearer. This commit also
changes some assertEqual calls to use (actual, expected) order and fix
some pyflakes warnings.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All code (util.byte_compile, build_py, install_lib) can now create .pyc
and/or.pyo files according to options given by users, without
interference from the calling Python?s own optimize mode or from the
sys.dont_write_bytecode switch.
The rationale is that packaging gives control over the creation of
.pyc/.pyo files to the user with its own explicit option, and the
behavior should not be changed if the calling Python happens to run with
-B or -O for whatever reason.
This is actually a bug fix, not an improvement: Digging into the early
history of distutils shows that the original author wanted this behavior
(see for example comments in build_py in r12940).
|
| |/
|
|
|
|
|
|
| |
I?ve made more edits than the bug report suggested to make sure the
generated setup script is compatible with many Python versions; a
comment in the source explains that in detail.
Thanks to David Barnett for the report and original patch.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This file is needed in other tests, so it?s better to have the support
code in tests.support. It?s also simpler to just have a skip instead of
custom print/return/test suite fiddling. Unfortunately, the xxmodule.c
file (resurrected from the repo, and also identical to the version in
Python 2.7) cannot be compiled by Python 2.4 and 2.5 on my computer, so
the test is skipped.
The code to fix up build_ext for Unix shared builds and Windows debug
builds was also moved to support for future reuse.
Finally, I fixed code using sysconfig._CONFIG_VARS directly so that it
calls get_config_var first, so that _CONFIG_VARS is a dict instead of
None.
|
| |
|
|
|
|
|
|
|
|
| |
This commit adds some missing names found by pyflakes/pylint; the test
suite passed before, but we might as well have correct code. Some other
functions have been removed; running the test suite through
d2.tests.__main__ now requires Python 2.7.
There?s still quite a bit of unnecessary duplication between __init__
and support, but I won?t fix that now.
|
| |
|
|
|
|
|
|
|
|
| |
shutil, sysconfig, tarfile and their tests have been updated to the
latest 3.2 version (except for test_tarfile which is not backported yet)
and edited to be compatible with 2.4.
Duplicates added in util during the Great Update have been deleted, as
well as functions I removed recently in packaging. Unneeded modules in
_backport have been deleted or moved to d2.compat.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This caused pysetup to print out tuples. When multi-line strings are
enclosed in parens for line-wrapping purposes, which would not print out
a tuple, I have added a space for clarity anyway.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Logging calls have the signature (msg, *args, **kwargs) so that the
%-formatting can be delayed until it is needed. Logger objects also have an
isEnabledFor method that can be used to isolate expensive code.
Next steps: use only one of d2.logger methods or logging module functions;
use a proper handler in our test machinery instead of monkey-patching; remove
cmd.warn and cmd.announce and use logging instead. TODOs have been added in
the modules and on the wiki.
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The unittest module is selectively imported from the standard library
if we're running with a Python >= 3.2 or from and external library
otherwise. This logic was moved from distutils2.test.support to
distutils2.tests because the former module also imports various
modules from distutils2, which would skew the coverage measurement
because the definitions in those module would run before the
instrumentation had a chance to be started.
|
| | |
|
| |
|
