| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Assertion error message had typos in arguments to string format.
.cover files for modules in packages are now put in the right place.
The code that generate .cover files seemed to prepend a "./" to many
absolute paths, causing them to fail. The code now checks explicitly
for absolute paths and leaves them alone.
In trace/coverage code, recover from case where module has no __name__
attribute, when e.g. it is executed by PyRun_String(). In this case,
assign modulename to None and hope for the best. There isn't anywhere
to write out coverage data for this code anyway.
Also, replace several sys.stderr.writes with print >> sys.stderr.
New features:
-C/--coverdir dir: Generate .cover files in specified directory
instead of in the directory where the .py file is.
-s: Print a short summary of files coverred (# lines, % coverage,
name)
|
| |
|
|
|
|
| |
(Yes, this is a new feature right before the 2.1 release. No, I can't
imagine this would seriously break anybody's code. In fact, most
users of this script are probably *happy* to see this addition.)
|
| | |
|
| | |
|
| |
|
|
|
|
| |
this just copies the __name__=='__main__' logic from pydoc.py.
?!ng can decide whether he wants to create a main() in pydoc, or rip
it out of pydoc.py completely.
|
| |
|
|
|
|
|
|
|
| |
Guido told me to do this <wink>.
Greatly expanded docstrings, and fleshed out with examples.
New std test.
Added new get_close_matches() function for ESR.
Needs docs, but LaTeXification of the module docstring is all it needs.
\CVS: ----------------------------------------------------------------------
|
| |
|
|
|
|
|
|
|
|
|
| |
\t\t\t\t\treal code
##\t\t\t\t\tunused code
\t\t\t\t\treal code
via untabifying and shifting the real code left. Semantically the
same but made the intent of the commented-out-in-column-0 unused code
unclear. The exact same unused code appears to have gotten copied from
file to file over the years.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
codec to not apply Latin-1 mappings for keys which are not found
in the mapping dictionaries, but instead treat them as undefined
mappings.
The patch was originally written by Martin v. Loewis with some
additional (cosmetic) changes and an updated test script
by Marc-Andre Lemburg.
The standard codecs were recreated from the most current files
available at the Unicode.org site using the Tools/scripts/gencodec.py
tool.
This patch closes the bugs #116285 and #119960.
|
| |
|
|
| |
after implementing it I liked Gregor's two-"?" line idea a lot.
|
| |
|
|
| |
ndiff w/ a custom version I made for Guido during the pre-2.0 freeze.
|
| |
|
|
|
|
|
| |
somewhat useful to learn regular expressions, and this way it'll be
installed on Windows.
This closes bug report 115609.
|
| | |
|
| | |
|
| |
|
|
| |
__name__ == '__main__'. Closes SF bug #110844.
|
| |
|
|
| |
This should match the situation in the 1.6b1 tree.
|
| | |
|
| | |
|
| |
|
|
| |
change eliminate to delete (-d)
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
mislabeled.
(Using -c and then -e rearranges some comments, so I won't check that
in -- but it's a good test anyway.
Note that pindent is not perfect -- e.g. it doesn't know about
triple-quoted strings!)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
A Python program can be completed and reformatted using
Tools/scripts/pindent.py. Unfortunately there is no option for removal
of the generated "# end"-tags. Although a few Python commands or a
"grep -v '# end '" can do wonders here, there are two drawbacks:
- not everyone has grep/time to write a Python script
- it is not checked whether the "# end"-tags were used validly
Solution:
add extra option "-e" (eliminate) to pindent.py
|
| |
|
|
| |
Typo noted by /F.
|
| |
|
|
| |
Detlef Lannert <lannert@lannert.rz.uni-duesseldorf.de>.
|
| |
|
|
| |
gencodec.py - Create Python codecs from Unicode mapping files
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
* In crlf.py and lfcr.py: regsub -> re
|
| |
|
|
|
|
| |
* In logmerge.py: added '-r' flag to show the oldest checkin
first instead of the newest, and getopt.getopt was used
wrong.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"""
If the filename being complained about contains a space, enclose the
file-name in quotes.
The reason is simply that when I try and parse tabnanny's output, filenames
with spaces make it very difficult to determine where the filename stops
and the linenumber begins!
"""
Tim approves.
I slightly changed the patch (use 'in' instead of string.find()) and
arbitrarily bumped the __version__ variable up to 6.
|
| |
|
|
|
| |
Don't rewrite the file in place.
(Reported by Andy Dustman.)
|
| |
|
|
| |
main() when imported (in other words, it is not usable as a module).
|
| |
|
|
|
|
|
|
| |
I should have waited overnight <wink/sigh>. Nothing wrong with the one I
sent, but I couldn't resist going on to add new -r1 / -r2 cmdline options
for recreating the original files from ndiff's output. That's attached, if
you're game! Us Windows guys don't usually have a sed sitting around
<wink>.
|
| |
|
|
|
|
|
| |
Attached is a cleaned-up version of ndiff (added useful module
docstring, now echo'ed in case of cmd line mistake); added -q option
to suppress initial file identification lines; + other minor cleanups,
& a slightly faster match engine.
|
| |
|
|
| |
killed. Discard the error in that case, but propogate it otherwise.
|
| |
|
|
| |
offending files to be printed. Good for emacs `tabnanny.py *.py`
|
| |
|
|
|
| |
BeOS headers live in various non-standard places;
luckily, there's an environment variable that lists them all.
|
| |
|
|
|
|
|
|
|
| |
"""
the NEWS file of Python 1.5.2a2 inspired me to look at
Tools/scripts/untabify.py. I wonder why it accepts a -t argument
but ignores it. The following patch tries to make it somewhat useful
(i.e., to override the tabsize=8 setting). Is that agreeable?
"""
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
