New submission from Rob Taft :
Whenever I try to patch flask.g, it appears to do nothing. This happened when
I upgraded mock from 3.x to 4.x. I reported it on the mock github page
https://github.com/testing-cabal/mock/issues/490 and was asked to report it
here. The folllowing code run
Rob Taft added the comment:
The test was supposed to patch the flask component during the unit test,
the error indicates the patch did not work. The actual error message is
not relevant to the actual issue. I don't know why I was directed to here.
When I replace it with unittest.moc
Rob Taft added the comment:
I have confirmed that using unittest.mock instead of the 3rd party mock library
in python 3.8.3 and 3.9-dev fails to patch flask.g. 3.7.7 works correctly.
--
___
Python tracker
<https://bugs.python.org/issue40
Change by Rob Taft :
--
versions: +Python 3.9 -Python 3.6
___
Python tracker
<https://bugs.python.org/issue40805>
___
___
Python-bugs-list mailing list
Unsub
Rob Taft added the comment:
I updated the test with 2 cases and the traceback is different for each when I
expected them to be the same if this was purely a mock issue, the line throwing
the error is the same. I can post this over with flask and see what they think.
from unittest.mock
Rob Taft added the comment:
https://github.com/pallets/flask/issues/3637
I've worked around the issue and accept that this will not work in the future.
--
status: open -> closed
___
Python tracker
<https://bugs.python.org
