| 2019-07-03 22:48:33 |
peter green |
bug |
|
|
added bug |
| 2019-07-03 22:50:53 |
peter green |
mu-editor (Ubuntu): status |
New |
Fix Released |
|
| 2019-07-04 00:32:10 |
peter green |
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.
[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. |
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. |
|
| 2019-07-04 00:35:15 |
peter green |
attachment added |
|
mu-editor.debdiff https://bugs.launchpad.net/ubuntu/+source/mu-editor/+bug/1835320/+attachment/5274969/+files/mu-editor.debdiff |
|
| 2019-07-04 00:36:27 |
peter green |
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.
[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. |
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 ????
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. |
|
| 2019-07-04 00:40:55 |
Unit 193 |
nominated for series |
|
Ubuntu Disco |
|
| 2019-07-04 00:40:55 |
Unit 193 |
bug task added |
|
mu-editor (Ubuntu Disco) |
|
| 2019-07-04 00:53:28 |
peter green |
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 ????
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. |
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 ????
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. |
|
| 2019-07-04 00:55:04 |
peter green |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2019-07-04 02:00:01 |
peter green |
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 ????
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. |
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. |
|
| 2019-07-04 18:15:54 |
Mathew Hodson |
mu-editor (Ubuntu): importance |
Undecided |
Low |
|
| 2019-07-04 18:15:57 |
Mathew Hodson |
mu-editor (Ubuntu Disco): importance |
Undecided |
Low |
|
| 2019-07-05 09:14:52 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2019-07-05 09:15:03 |
Robie Basak |
mu-editor (Ubuntu Disco): status |
New |
Triaged |
|
| 2019-07-05 09:55:28 |
peter green |
attachment added |
|
mu-editor.debdiff https://bugs.launchpad.net/ubuntu/+source/mu-editor/+bug/1835320/+attachment/5275240/+files/mu-editor.debdiff |
|
| 2019-07-05 10:10:45 |
Robie Basak |
mu-editor (Ubuntu Disco): status |
Triaged |
In Progress |
|
| 2019-07-05 10:10:54 |
Robie Basak |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2019-07-08 22:58:56 |
Brian Murray |
mu-editor (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-07-08 22:59:01 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-07-08 22:59:03 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-07-08 22:59:06 |
Brian Murray |
tags |
|
verification-needed verification-needed-disco |
|
| 2019-07-09 03:05:18 |
peter green |
tags |
verification-needed verification-needed-disco |
verification-done-disco verification-needed |
|
| 2019-07-15 08:14:58 |
Launchpad Janitor |
mu-editor (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-07-15 08:15:00 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
