** Description changed: The "debug" function in mu-editor is broken in the version shipped in Ubuntu disco. Since mu is intended as a tool for teaching beginner programmers this servely limits it's usefulness. Nick Morrot and I have already fixed this in sid and the fix from sid has already migrated to buster and eoan. [Test Case] Install mu-editor and run it through the programs menu. Make sure you are in "python 3" mode. On the first run a box should pop up to select the mode. On later runs you can change mode through the ???? Write a small python program and click on the debug button. The expected behavior is that debugging starts, but instead > Traceback (most recent call last): > > File "/usr/share/mu-editor/mu/mu-debug.py", line 4, in <module> > > from mu.app import debug > > ModuleNotFoundError: No module named 'mu' [Analysis] This is a python path issue. mu-editor's python modules are installed under /usr/share/mu-editor/ . The main editor binary is installed in /usr/share/mu-editor and so finds the modules successfully though sys.path[0], however the debugger script is installed in /usr/share/mu- editor/mu and so does not find the modules. The fix is to tweak sys.path in the debugger script before loading mu modules. [Regression Potential] Potential for regression seems minimal. mu-editor is a leaf package and written in pure python. The debugger script in question is currently unusable. + + When comparing the old and new binaries the only changes I could find other + than the intentional one were some date stamp changes on some image files + and some html footer changes as a result of a new sphinx version. Neither of + these seem likely to cause regressions.
** Patch added: "mu-editor.debdiff" https://bugs.launchpad.net/ubuntu/+source/mu-editor/+bug/1835320/+attachment/5274969/+files/mu-editor.debdiff ** Description changed: The "debug" function in mu-editor is broken in the version shipped in Ubuntu disco. Since mu is intended as a tool for teaching beginner programmers this servely limits it's usefulness. - Nick Morrot and I have already fixed this in sid and the fix from sid - has already migrated to buster and eoan. + Nick Morrot and I have already fixed this in sid and the fix from sid has already migrated to buster and eoan. I would like to see this fixed in disco + too. [Test Case] Install mu-editor and run it through the programs menu. Make sure you are in "python 3" mode. On the first run a box should pop up to select the mode. On later runs you can change mode through the ???? Write a small python program and click on the debug button. The expected behavior is that debugging starts, but instead > Traceback (most recent call last): > > File "/usr/share/mu-editor/mu/mu-debug.py", line 4, in <module> > > from mu.app import debug > > ModuleNotFoundError: No module named 'mu' [Analysis] This is a python path issue. mu-editor's python modules are installed under /usr/share/mu-editor/ . The main editor binary is installed in /usr/share/mu-editor and so finds the modules successfully though sys.path[0], however the debugger script is installed in /usr/share/mu- editor/mu and so does not find the modules. The fix is to tweak sys.path in the debugger script before loading mu modules. [Regression Potential] Potential for regression seems minimal. mu-editor is a leaf package and written in pure python. The debugger script in question is currently unusable. When comparing the old and new binaries the only changes I could find other than the intentional one were some date stamp changes on some image files and some html footer changes as a result of a new sphinx version. Neither of these seem likely to cause regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835320 Title: mu-editor python debugger broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mu-editor/+bug/1835320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
