summaryrefslogtreecommitdiff
path: root/distutils2/command/build_py.py
Commit message (Collapse)AuthorAgeFilesLines
* Merge compat/_backport cleanup from default.?ric Araujo2011-11-231-1/+2
|\ | | | | | | | | | | 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.
* \ Ye olde merge.?ric Araujo2011-11-121-48/+29
|\ \ | |/ | | | | | | 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.
| * Improve byte-compilation to be independent of -O or -B.?ric Araujo2011-11-121-43/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
* | Start a branch to provide Distutils2 for Python 3.?ric Araujo2011-09-241-2/+2
|/ | | | | | | | | | 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.
* Fix the backport fixes.?ric Araujo2011-09-181-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Backported packaging from cpython default, overwriting previous version.Vinay Sajip2011-08-181-28/+27
|
* fix pysetup testsTarek Ziade2011-03-131-1/+4
|
* Fix two NameErrors (#11057)?ric Araujo2011-01-291-2/+3
|
* simplified the package_dir option - just one root dir allowedTarek Ziade2011-01-291-37/+9
|
* Save up a bit of memory thanks to dict.iter* and __iter__?ric Araujo2010-12-171-1/+1
|
* removed core.pyTarek Ziade2010-10-251-1/+1
|
* removed the __revision__ tag, that are specific to SVNTarek Ziade2010-10-041-1/+0
|
* moved everything in the same dir - we want to include docs/ in the releaseTarek Ziade2010-09-191-0/+436