| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
package_dir must be converted from the distutils path conventions to
local conventions before being used by build_py.
Fixes SF bug #509288, probably a candidate for 2.2.1
|
| |
|
|
|
|
|
|
|
|
|
| |
by default (since compiling at install time works just fine). Details:
- added 'compile' and 'optimize' options
- added 'byte_compile()' method
- changed 'get_outputs()' so it includes bytecode files
A lot of the code added is very similar to code in install_lib.py;
would be nice to factor it out further.
|
| |
|
|
|
|
| |
on the module file -- could be useful for subclasses overriding it.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Changed 'core.setup()' so it sets them to reasonable defaults.
Tweaked how the "usage" string is generated: 'core' now provides
'gen_usage()', which is used instead of 'USAGE'.
Modified "build_py" and "sdist" commands to refer to
'self.distribution.script_name' rather than 'sys.argv[0]'.
|
|
|
|
|
| |
represents packages as strings, not tuples. This allowed a simplification
in 'get_package_dir()', too -- can now assume that 'package' is a string.
|
|
|
|
| |
(and in order to generate a more sensible error message cleanly).
|
|
|
|
|
|
|
|
|
|
|
| |
attempt to verify the bold assertions in the documentation):
* entries for the "root package" in 'package_dir' didn't work --
fixed by improving the fall-through code in 'get_package_dir()'
* __init__.py files weren't installed when modules-in-packages
were listed individually (ie. in 'py_modules' in the setup script);
fixed by making 'check_package()' return the name of the __init__
file if it exists, and making 'find_modules()' add an entry to
the module list for __init__ if applicable
|
| |
|
| |
|
|
|
|
|
| |
timestamps), so every build_* command has 'self.force', which follows the
'build' command if not set by the user.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A host of improvements in preparation for the 'bdist' command:
- added 'get_outputs()' method (all the other improvements were to support
this addition)
- made 'find_package_modules()' and 'find_modules()' return similar
values (list of (package, module, module_filename) tuples)
- factored 'find_all_modules()' out of 'get_source_files()' (needed
by 'get_outputs()')
- factored 'get_module_outfile()' out of 'build_module()' (also needed
by 'get_outputs()')
- various little tweaks, improvements, comment/doc updates
|
| |
|
| |
|
| |
|
|
|
|
| |
'set_final_options()' to 'finalize_options()'.
|
| |
|
|
|
|
|
| |
command itself: no more of this "FooBar class for foo_bar command"
silliness.
|
| |
|
|
|
|
|
|
|
| |
'--help-commands' option).
Shuffled imports around in a few command modules to avoid expensive
up-front import of sysconfig (and resulting delays in generating list
of all commands).
|
| |
|
|
|
|
|
|
|
|
| |
install) the setup script itself.
Fixed 'build_module()' so we do *not* preserve file mode (which means
we can install read-only files, which makes the next installation
of this distribution fail -- at least under Unix); added a comment
explaining this.
|
|
|
|
|
|
|
|
| |
Bunch of little bug fixes that appeared in building non-packagized
distributions. Mainly:
- brain-slip typo in 'get_package_dir()'
- don't try to os.path.join() an empty path tuple -- it doesn't like it
- more type-safety in 'build_module()'
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't call 'set_final_options()' in 'run()' anymore -- that's now
guaranteed to be taken care of for us by the Distribution instance.
Rearranged to bit to allow outsiders (specifically, the 'dist' command)
to find out what modules we would build:
- 'find_modules()' renamed to 'find_package_modules()'
- most of 'build_modules()' abstracted out to 'find_modules()'
- added 'get_source_files()' (for the 'dist' command to use)
- drastically simplified 'build_modules()' -- now just a wrapper around
'find_modules()' and 'build_module()'
|
|
|
|
| |
packages and searching for source files by 'package_dir'.
|
| |
|
|
|
|
|
| |
we no longer explicitly pull distribution options out of our Distribution
object, but rather let the Distribution put them into the command object.
|
| |
|
|
|
|
|
|
|
|
|
| |
of the 'install_py' command rather than 'build_py'. Obviously, this
meant that the 'build_py' and 'install_py' modules had to change; less
obviously, so did 'install' and 'build', since these higher-level
commands must make options available to control the lower-level
commands, and some compilation-related options had to migrate with the
code.
|
|
|
|
|
| |
and 'make_file()'-- that way, the verbose and dry-run flags are
handled for free.
|
|
|