| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| | |
Independently found and fixed by me (with help from Luis Rojas) and
Janusz Lewandowski.
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | | |
|
| | |
| |
| |
| | |
pysetup list, pysetup graph and installation log
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| |/
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| | |
hasattr is subtly wrong, as special methods are looked up on the class,
and given that the callable builtin is back in Python 3.2 we may as well
use it. Regular users shouldn?t see the DeprecationWarnings, and us
developers can just ignore thme when running tests.
|
| |\ \
| |/ |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When called without option (?-f field? or ?--all?), ?pysetup metadata?
didn?t do anything useful. Now it prints out all metadata fields.
?pysetup list? without arguments already printed all installed
distributions found, so the option was superfluous. Less typing, more
consistency, more happiness!
In addition, change ?releases? for ?projects? in the description of the
list action. Strictly speaking, one installed distribution satisfies
the requirement for a release (i.e. version) of a project, but as
currently only one release per project can be installed at a time, the
two are somewhat equivalent, and ?project? is more understandable in
help texts (which call their argument ?dist?, by the way..)
Finally, all help texts have been moved near to the function they
document.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |\ |
|
| | |\ \ |
|
| | | | | |
|
| | |/ / |
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
