summaryrefslogtreecommitdiffstats
path: root/Lib/distutils/command/build_scripts.py
Commit message (Collapse)AuthorAgeFilesLines
* Make setup.py less chatty by default.Jeremy Hylton2002-06-041-3/+4
| | | | | | | | | | | | | | | This is a conservative version of SF patch 504889. It uses the log module instead of calling print in various places, and it ignores the verbose argument passed to many functions and set as an attribute on some objects. Instead, it uses the verbosity set on the logger via the command line. The log module is now preferred over announce() and warn() methods that exist only for backwards compatibility. XXX This checkin changes a lot of modules that have no test suite and aren't exercised by the Python build process. It will need substantial testing.
* Allow shebang's which use versioned Python binaries. FixesMarc-André Lemburg2002-02-281-1/+1
| | | | bug #521526.
* Joe VanAndel wrote:Marc-André Lemburg2001-12-111-1/+1
| | | | | | | | | | | > > When using 'distutils' (shipped with Python 2.1) I've found that my > Python scripts installed with a first line of: > > #!/usr/bin/python2.1None > > This is caused by distutils trying to patch the first line of the python > script to use the current interpreter.
* Fix forMichael W. Hudson2001-12-101-2/+11
| | | | [ #409430 ] pydoc install broken
* [Bug #475009] Tighten the pattern for the first line, so we don'tAndrew M. Kuchling2001-12-061-1/+1
| | | | adjust it when a versioned interpreter is supplied (#!.../python2 ...)
* Remove unused variableAndrew M. Kuchling2001-08-101-1/+0
|
* Do convert_path() on script paths (now PyXML builds out of the boxJust van Rossum2001-07-291-0/+2
| | | | under MacOS.)
* Undo revision 1.7: always mangle a #! line containing "python" to pointGreg Ward2001-07-251-4/+2
| | | | | | | | | | | | | | to the current Python interpreter (ie. the one used for building/installation), even (especially!) if "/usr/bin/env" appears in the #! line. Rationale: installing scripts with "#!/usr/bin/env python" is asking for trouble, because 1) it might pick the wrong interpreter (not the one used to build/install the script) 2) it doesn't work on all platforms (try it on IRIX 5, or on Linux with command-line options for python) 3) "env" might not be in /usr/bin
* When not copying a file because the output is up to date, make the messageFred Drake2001-03-021-2/+2
| | | | | slightly more brief, and more like the message that an extension will not be built because the built copy is up to date.
* Leave #! lines featuring /usr/bin/env aloneAndrew M. Kuchling2001-02-281-2/+4
|
* Standardized whitespace around function calls.Greg Ward2000-09-301-3/+3
|
* Added 'boolean_options' list to support config file parsing.Greg Ward2000-09-251-0/+2
|
* Fixed a grab-bag of typos spotted by Rob Hooft.Greg Ward2000-07-271-1/+1
|
* Take the basename of the script before concatenating it with the build dir.Greg Ward2000-05-251-1/+1
|
* Improvements to Bastian's build_scripts command:Greg Ward2000-05-251-31/+58
| | | | | | | | | * 'first_line_re' loosened up * command description improved * replaced '_copy_files()' and '_adjust_files()' with one method that does everything, 'copy_scripts()' -- this should be more efficient than Bastian's version, should behave better in dry-run mode, and does timestamp dependency-checking
* Bastian Kleineidam: the "build_scripts" command.Greg Ward2000-05-251-0/+71
generated by cgit v0.12 at 2024-11-22 04:25:16 (GMT)