| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
translating an old PKG-INFO
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Change the fixers used in tests to something not provided by lib2to3
- Test conversion of doctests in text files
- Factor out test boilerplate into a common method
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
| |
The code is still ugly, but at least it works better now. Patches to
make it easier to read are welcome, as well as support in #12915.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| | |
A new function, get_metadata_version, replaces the metadata.version attribute as the preferred method of retrieving the metadata version.
The metadata_to_dict function has been relocated from distutils2.util to distutils2.metadata to help improve organization.
|
| | |
| |
| |
| |
| |
| | |
iblog now raise ValueError when riche iglob are malformated.
Related test are included in this changeset.
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Using the :
handle = open()
try:
...
finally:
handle.close()
as advised by Eric Araujo.
Also, instead of several calling to handle.write(), use a multi-line string.
|
| | | | |
|
| |\ \ \
| |/ / |
|
| | |/ |
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
That way, distribution maintainers will be able to offer distutils & distutils2
compatibility, without having to maintain the same information in two files.
The only that needs to be maintained is the setup.cfg. Indeed, the setup.py
reads the setup.cfg file every time it is called, to determine which are the
correct args to pass on to distutils.core.setup().
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
