[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

https://bugs.kde.org/show_bug.cgi?id=378083 Francis Herne changed: What|Removed |Added CC||antonis+kdebugs@metadosis.g

[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

https://bugs.kde.org/show_bug.cgi?id=378083 Francis Herne changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde

[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

https://bugs.kde.org/show_bug.cgi?id=378083 --- Comment #4 from Diego Garcia --- Heh never thought about putting functions in the middle. Yes, that works. It could be a good workaround for new code. It'd be great if it could be fixed though -- You are receiving this mail

[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

https://bugs.kde.org/show_bug.cgi?id=378083 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk

[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

https://bugs.kde.org/show_bug.cgi?id=378083 --- Comment #2 from Diego Garcia --- The problem is that when you want to call the inner function or return it, it will also get flagged as an error. And it would be correct since this code fails. --- def test_closures(): this

[kdev-python] [Bug 378083] Variables from parent function in closures are considered undefined

https://bugs.kde.org/show_bug.cgi?id=378083 --- Comment #1 from Sven Brauch --- Yeah, this is a difficult case. In my opinion the current behaviour is ok: you cannot sensibly call the function before defining the variable, so you can just as well re-order your code to define