2TO3-2.7(1) User Commands 2TO3-2.7(1)NAME
2to3-2.7 - manual page for 2to3-2.7 2.7
SYNOPSIS
2to3 [options] file|dir ...
OPTIONS -h, --help
show this help message and exit
-d, --doctests_only
Fix up doctests only
-f FIX, --fix=FIX
Each FIX specifies a transformation; default: all
-j PROCESSES, --processes=PROCESSES
Run 2to3 concurrently
-x NOFIX, --nofix=NOFIX
Prevent a transformation from being run
-l, --list-fixes
List available transformations
-p, --print-function
Modify the grammar so that print() is a function
-v, --verbose
More verbose logging
--no-diffs
Don't show diffs of the refactoring
-w, --write
Write back modified files
-n, --nobackups
Don't write backups for modified files
2to3-2.7 2.7 May 2011 2TO3-2.7(1)
Check Out this Related Man Page
COMBINEDIFF(1)COMBINEDIFF(1)NAME
combinediff - create a cumulative unified patch from two incremental patches
SYNOPSIS
combinediff [-p n] [-U n] [-d PAT] [-Bbiqwz]
[--interpolate | --combine] diff1 diff2
combinediff {--help | --version}
DESCRIPTION
combinediff creates a unified diff that expresses the sum of two diffs. The diff files must be listed in the order that they are to be
applied. For best results, the diffs must have at least three lines of context.
The diffs may be in context format. The output, however, will be in unified format.
OPTIONS -p n When comparing filenames, ignore the first n pathname components from both patches. (This is similar to the -p option to GNU
patch(1).)
-q Quieter output. Don't emit rationale lines at the beginning of each patch.
-U n Attempt to display n lines of context (requires at least n lines of context in both input files). (This is similar to the -U option
to GNU diff(1).)
-d pattern
Don't display any context on files that match the shell wildcard pattern. This option can be given multiple times.
Note that the interpretation of the shell wildcard pattern does not count slash characters or periods as special (in other words, no
flags are given to fnmatch). This is so that ``*/basename''-type patterns can be given without limiting the number of pathname com-
ponents.
-i Consider upper- and lower-case to be the same.
-w Ignore whitespace changes in patches.
-b Ignore changes in the amount of whitespace.
-B Ignore changes whose lines are all blank.
-z Decompress files with extensions .gz and .bz2.
--interpolate
Run as ``interdiff''. See combinediff(1) for more information about how the behaviour is altered in this mode.
--combine
Run as ``combinediff''. This is the default.
--help Display a short usage message.
--version
Display the version number of combinediff.
BUGS
The -U option is a bit erratic: it can control the amount of context displayed for files that are modified in both patches, but not for
files that only appear in one patch (which appear with the same amount of context in the output as in the input).
SEE ALSO interdiff(1)AUTHOR
Tim Waugh <twaugh@redhat.com>.
patchutils 17 Apr 2002 COMBINEDIFF(1)
Right, noob to shell scripting, playing a round for practice, wrote the following but it doesn't seem to work as expected, how could I fix/improve this script?
#!/bin/bash
#set -v
#set -x
case $# in
1)
echo Searching for $1 in '*';
find . -iname '*' 2>/dev/null | xargs grep "$1" -sl... (3 Replies)
Actually I have installed python 3.2.
It seems there are a lot of synta variance between 2.2 and 3.2.
Is it possible to run a script in 2.2 without actually installing 2.2.
But I have installed 3.2.
and also is it possible to access the 2.2 shell in 3.2 version.
I am naive in python .
Please... (1 Reply)
Upon opening Terminal I get the following message:
-bash: /usr/bin/manpath: No such file or directory
-bash: /usr/bin/perl: No such file or directory
-bash: grep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: grep: command not found
I searched... (9 Replies)
Mac users...
I updated this MBP from OSX 10.12.1 to the brand new OSX 10.12.2 two days ago.
A week ago I installed the Xcode suite.
Now the QT shell audio capture in another recent thread is broken when exporting a file.
It gives an error in a window, paraphrasing, The action is not... (4 Replies)
Hello everyone,
I have just started python, and there is something that escapes me. I don't understand why my little script doesn't work.
When I do, it work:
my_string = "bonjour"
if len(my_string) < "6":
print(my_string + " < 6")
else:
print(my_string + " > 6")
... (2 Replies)
I am new to shell scripting and I ran into a couple lines of code which I don't completely understand:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/entity/bin
data_dir=/usr/local/entity/projectI believe data_dir to be a more conventional link to a directory. However, I am not sure what PATH... (12 Replies)