David Antonini added the comment:
Somehow I missed the follow up here until now. I don't remember the original
code, but I'm fairly confident that mocked_print is the patched print function
eg
with patch('dionysus_app.class_functions.print') as mocked_print:
Probably s
David Antonini added the comment:
Apologies for initial malformed message, I hit submit prematurely.
--
___
Python tracker
<https://bugs.python.org/issue35
David Antonini added the comment:
I'm having a problem with mock.call when I import it directly from
unittest.mock.
When I do:
from unittest.mock import patch, mock_open, call
mocked_print.assert_has_calls([
call("first print"),
call("second print"),
New submission from David Antonini :
Ok so that's a pretty odd bug. I already had from unittest.mock import patch,
mock_open so I simply modified that to from instead of doing mock.call in my
test. Changing this to from unittest import mock and then mock.call fixed the
error.
David Antonini added the comment:
Does the Unicode documentation currently conform to that convention, or does it
require editing?
It appears to me that a lot of cases where reference to "Unicode object" is
currently capitalised (most of them, in fact) may need to be modified.
H
New submission from David Antonini :
Make 'unicode'/'Unicode' capitalization consistent.
'Unicode' is a proper noun, and as such should be capitalized.
I submitted a pull request correcting the inconsistent capitalization in the
Unicode page of the Documen
