| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |\ |
|
| | | | |
|
| | |/ |
|
| | |
| |
| |
| | |
effect, --force option has been removed
|
| | | |
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 :)
|
| | |
| |
| |
| |
| |
| | |
This fixes a regression from distutils, where ?setup.py --help-commands?
prints out commands grouped by topic (i.e. building vs. installing),
which is more useful than using sorted.
|
| |\ \
| |/
| |
| |
| |
| | |
For some reason, the diff for distutils/_backport/misc.py makes it seem
like it?s a new file instead of showing the changes I did during the
merge.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves individual backported functions from compat into a new
_backport.misc module. compat regains its original purpose of
containing 2to3 support code (i.e. compat for projects using distutils2,
not internal compat for d2 code) and all backports now live under the
private _backport subnamespace.
Also fix the definition of ?any? to bind it to the builtin in 2.5+
(fsencode and detect_encoding not changed, they never exist in
2.x).
|
| |\ \
| |/
|/| |
|
| | |\
| | |
| | |
| | |
| | | |
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.
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | |_|/
|/| | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Remove __main__ blocks obsoleted by pysetup
- Fix typo ?seperate?
- Add one test that was promised but not written
- Reorganize one file
|
| | | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
| | |/
|/| |
|
| | |
| |
| |
| | |
This was not broken in d2 because codecs.open allows 'b' in mode.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is copied from the namesake distutils command; I can?t test the
change but it should be okay, as Python 3 users have tested the
distutils command.
|
| |
|
|
|
|
|
| |
In dry-run mode, commands should log the same info as in real operation
and should collect the same files in self.outputs, so that users can run
a command in verbose and dry-run mode to see exactly what operations
will be done in the real run.
|
| | |
|
| |
|
|
|
|
| |
There was already a test for this, but it was complicated and had a
subtle bug (custom command objects need to be put in dist.command_obj so
that other command objects may see them) that rendered it moot.
|
| |
|
|
|
|
| |
d2 uses the shutil.make_archive function (moved from distutils),
which does not support compress. There is no test to check that
?bdist --format whatever? works, so this slipped by.
|
| | |
|
| |
|
|
|
|
|
| |
- Rename an attribute and create it in initialize_options instead of
finalize_options to match the other install_* classes
- Remove unnecessary method call in tests
- Fix typo/wording in help text
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backports:
- sysconfig is now always imported from our backports
- when hashlib is not found, our backport is used instead of the md5
module (debatable; we could just drop hashlib)
Version-dependent features:
- PEP 370 features are only enabled for 2.6+
- the check for sys.dont_write_bytecode was fixed to use getattr
with a default value instead of hasattr
Idioms/syntax:
- octal literals lost their extra 0
- misused try/except blocks have been changed back to try/finally
(it?s legal in 2.4 too, it?s only try/except/finally that isn?t)
- exception catching uses the regular 2.x idiom instead of sys.exc_info
- file objects are closed within finally blocks (this causes much
whitespace changes but actually makes diff with packaging easier)
Renamed modules:
- some missed renamings (_thread, Queue, isAlive, urllib.urlsplit, etc.)
were fixed
Other:
- a few false positive replacements of ?packaging? by ?distutils2? in
comments or docstrings were reverted
- util.is_packaging regained its name
- assorted whitespace/comment/import changes to match packaging
|
| |\
| |
| |
| |
| |
| |
| | |
The print statement fixes that were in my branch override the print(u'')
calls added by Alexis; the import at function scope were removed for the
usual reasons; d2._backport.hashlib is used if hashlib is not available
instead of md5.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/
|
|
| |
install_distinfo to allow all metadata consumers access to them.
|
| | |
|
| | |
|
| | |
|
