You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 22, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 22, 2025. It is now read-only.
Commented lines of code changing eel behavior (actually) #706
Eel version
0.16.0 Describe the bug
Commented lines of code changes how Eel executes under very specific circumstances involving functions generated at runtime. These functions seem to require two eel.expose calls to be exposed properly, but only the first needs to execute. The second can be commented.
I'm not sure if the code I'm writing should work or not, but it definitely shouldn't do this.
The app will execute, and the python call will not generate an error, but the function will not be executed.
Expected behavior
The commented line should have no impact on code execution, as it is commented.
Additionally, it is strange that this functionality requires both of these eel.expose calls for the function to be exposed successfully. Neither expose alone works, but the second one can be commented and it will still work.
Is this even supposed to work? It is a somewhat strange use-case.
Activity