Closed coyotemarin closed 4 years ago
Never mind, the problem here is that MRGrepJob
had a required argument, so you couldn't run MRGrepJob()
.
There is not much practical reason to initialize a MRJob
with no arguments (usually you at least want input), so we could change the default behavior so that no args means to read from sys.argv
, rather than []
. This might perturb some tests.
mrjob/examples/mr_grep.py
ranMRGrepJob().run()
when invoked as a script, and this caused it to mysteriously lose the command line arguments. Changing it toMRGrepJob.run()
fixed it.Not sure if this is an existing bug, or one I introduced when merging
MRJobLauncher
intoMRJob
(see #2088).