You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, if a test contains the following code:
a = 1
b = 2
assert a == b
macOS outputs this:
assert a == b
AssertionError: assert 1 == 2
But Android doesn't show the values:
I/python.stdout: assert a == b
I/python.stdout: AssertionError
This is probably caused by some conflict between the Chaquopy importer and the Pytest assertion rewriting mechanism, which as I understand it, involves actually generating its own .pyc files with the modified bytecode.
In practice, it's usually easy to work around this with some extra logging or an explicit assert message, so it's not worth looking into just now.
The text was updated successfully, but these errors were encountered:
For example, if a test contains the following code:
macOS outputs this:
But Android doesn't show the values:
This is probably caused by some conflict between the Chaquopy importer and the Pytest assertion rewriting mechanism, which as I understand it, involves actually generating its own .pyc files with the modified bytecode.
In practice, it's usually easy to work around this with some extra logging or an explicit assert message, so it's not worth looking into just now.
The text was updated successfully, but these errors were encountered: