[issue25843] unexpected output using pythons ternary operator in combination with lambda

Tijs Van Oevelen added the comment: Apologies for not posting a summary of the bug. I really had no idea how to describe the problem, as it is over my head. I could only refer to my question on Stack Overflow that triggered the discovery of the bug. --

[issue25843] unexpected output using pythons ternary operator in combination with lambda

Tijs Van Oevelen added the comment: It's definitely also in 3.4 by the way. -- versions: +Python 3.4 ___ Python tracker ___

[issue25843] unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda

Changes by Tijs Van Oevelen : -- nosy: -Tijs Van Oevelen ___ Python tracker ___

[issue25843] unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda

New submission from Tijs Van Oevelen: The bug is described on Stack Overflow in length: http://stackoverflow.com/questions/34100732/unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda -- messages: 256229 nosy: Tijs Van Oevelen priority: normal severity: normal

[issue25843] unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda

R. David Murray added the comment: For reference, the minimal reproducer is: >>> f1, f2 = lambda: 1, lambda: 1.0 >>> f2() 1 The cause (according to the answer in the link) is that the two lambda's incorrectly compare as equal and end up sharing the same code object...one of the inequality

[issue25843] unexpected output using pythons ternary operator in combination with lambda

Changes by Ethan Furman : -- title: unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda -> unexpected output using pythons ternary operator in combination with lambda ___ Python tracker