I reduced the problem to the following code, which is reproducible without icecream.

from executing import Source
import inspect


print("\n\nFirst bug")
print(Source.executing(inspect.currentframe()).node)


def test_icecream_fine():
    print("No bug")
    print(Source.executing(inspect.currentframe()).node)
    assert (True)
    1

def test_icecream_also_fine():
    print("No bug")
    print(Source.executing(inspect.currentframe()).node)
    assert (True
    )
    

def test_icecream_bug():
    print("Second bug")
    print(Source.executing(inspect.currentframe()).node)

    assert (True # this linebreak is important
    ) 

    1 # this is also important

output

❯ pytest test_icecream.py -s
========================================= test session starts ==========================================
platform linux -- Python 3.10.0, pytest-7.2.0, pluggy-1.0.0
rootdir: /home/frank/projects/executing
collecting ...

First bug
None
collected 3 items

test_icecream.py No bug
<ast.Call object at 0x7f8013ba36d0>
.No bug
<ast.Call object at 0x7f8013ba32b0>
.Second bug
None
.

========================================== 3 passed in 0.02s ===========================================

Can this line have something to do with this behaviour?

executing/executing/executing.py

Lines 884 to 888 in 32c2388

    
           if not self.is_pytest: 
        
               checks += [ 
        
                   attrgetter('co_names'), 
        
                   attrgetter('co_varnames'), 
        
               ]

I don't know how the SentinelNodeFinder works. Any hints?

Weird failure with pytest and multiline assert #61

Description

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions