Closed ns-rorsten closed 1 month ago
@ns-rorsten Hm, I'll say both "I'm not sure why that is", and "well, better twice than never". ;).
I'll look in to it.
@ns-rorsten I think this is now fixed in the master development branch. Once tests all pass, I'll tag a new release.
Excellent, thank you for the quick response.
@ns-rorsten This should now be fixed.
In a project using asteval, a test that creates a NameError started failing with a doubled error count when I upgraded to 1.0.2. I see this addressed a problem with NameError handling, but:
For comparison, after downgrading to 1.0.1: