Builtin variable __file__ is set to jpydaemon.py (the debugger), and not to the file actually being debugged.
Is this a stopper bug? What does it mean in practice for the usability and usefulness of the debugger?
If something runs correctly outside of the debugger, but fails to run inside of the debugger, that to me is a complete
fail for the usability and usefulness of a debugger.
In particular, the first few lines of Google App Engine (dev_appserver.py) use the __file__ builtin to strip out the path
of the appserver module. When run in the debugger, this gives them the path of the netbeans jpydaemon module instead.
I agree this is a nasty bug, but I think it is worth it to release an updated Early Access release even with this bug
present. Moving priority to P2.
Should be solved with the new debugger when we add it. The debugger is currently disabled. Closing this since there is no point into importing it elsewhere.
Thanks for your evaluation Julien. Reporter, if you think your issue is still valid and needs to be addressed, don't hesitate to reopen it with additional information. Closing for now.