This avoids a name overlap with the system-installed copy of python. Since redo adds the redo/ dir to the $PATH before running .do files, python.do might see its own previously-created target instead of the "real" python when testing, and create an infinite loop by accident.
6 lines
205 B
Text
6 lines
205 B
Text
# make sure redo doesn't think merely *reading* the old file counts as
|
|
# modifying it in-place.
|
|
cat $1 >/dev/null 2>/dev/null || true
|
|
../../redo/py tick.py
|
|
cat $1 >/dev/null 2>/dev/null || true
|
|
echo hello
|