[Bug 1835320] Re: mu-editor python debugger broken.

[peter green]

** 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. 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
- ????
+ icon in the top left corner.
  
  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, there are no compiled binaries in the package
  that could be affected by the compiler version. The debugger script in
  question is currently unusable so there doesn't seem much potential for
  making it worse.
  
  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
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1835320

Title:
  mu-editor python debugger broken.

Status in mu-editor package in Ubuntu:
  Fix Released
Status in mu-editor source package in Disco:
  New

Bug description:
  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. 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 icon in the top left corner.

  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, there are no compiled binaries in the
  package that could be affected by the compiler version. The debugger
  script in question is currently unusable so there doesn't seem much
  potential for making it worse.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mu-editor/+bug/1835320/+subscriptions