Failed assertion explanation when using conditionals

Considering the following python file:

def myfunc():
    return 1

def test_nice():
    assert myfunc() == 0

def test_not_nice():
    assert myfunc() == 0 if True else 1

The second test test_not_nice does not have a nice explanation of the failure (where we get to see the value of myfunc), as we have in test_nice, even though they are basically the same in the end.

=================================== FAILURES ===================================
__________________________________ test_nice ___________________________________

    def test_nice():
>       assert myfunc() == 0
E       assert 1 == 0
E        +  where 1 = myfunc()

test_one.py:5: AssertionError
___________________________________ test_not_nice ___________________________________

    def test_not_nice():
>       assert myfunc() == 0 if True else 1
E       assert False

test_one.py:8: AssertionError
=========================== short test summary info ============================
FAILED test_one.py::test_nice - assert 1 == 0
FAILED test_one.py::test_not_nice - assert False
============================== 2 failed in 0.08s ===============================

It seems to me that the assertion rewriting could also evaluate the right handside of the == comparison just as it does with myfunc.

Tested in pytest 6.0.1

Reproduce the two examples from test_one.py, especially test_not_nice, using the assertion-rewriting behavior described for pytest 6.0.1. Start by tracing assertion rewriting for the conditional expression and comparison. Done means the conditional case provides a useful explanation that includes the evaluated value, comparable to test_nice.