capturemock recording badly quoted '''null''' that it can't replay
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CaptureMock |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Capturemock is recording something it can't then replay. It records:
<-PYT:subproces
->RET:Instance(
<-PYT:popen2.
->RET:("'''null'
"'', None)
<-PYT:popen2.
->RET:0
which causes this stacktrace when it tries to replay it:
File "/usr/local/
*args, **kw)
File "/usr/local/
return self.processRep
File "/usr/local/
return proxy.captureMo
File "/usr/local/
return eval(response, self.captureMoc
File "<string>", line 1
("'''null'
^
SyntaxError: EOL while scanning string literal
If I manually edit the recorded string to read:
<-PYT:subproces
->RET:Instance(
<-PYT:popen2.
->RET:(
<-PYT:popen2.
->RET:0
Then it works fine to replay it.
If I run this command on the command line, the output the program actually produces looks like this:
$ > /home/emilyb/
'null'
$ >
(followed by a newline)
Changed in capturemock: | |
status: | Fix Committed → Fix Released |
Checked in a fix. Problem was multiline string starting with a single quote.