Bug #60815 | Exception in Python workbench shell | ||
---|---|---|---|
Submitted: | 9 Apr 2011 11:06 | Modified: | 20 Jun 2011 19:23 |
Reporter: | Sylvain Plante | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.2.33 | OS: | Windows (Windows 7 ) |
Assigned to: | CPU Architecture: | Any | |
Tags: | exception, execute, python, script, shell |
[9 Apr 2011 11:06]
Sylvain Plante
[9 Apr 2011 11:09]
Sylvain Plante
Made a mistake in first place, level should be S1 instead of S3
[9 Apr 2011 11:34]
Sylvain Plante
Found a workaround. Instead of opening the script file, I created a new script file and then pasted the code in it. My script file was name «Test» with no extension.
[25 May 2011 23:09]
Alfredo Kojima
Hi Can you try with version 5.2.34 and see if the problem persists?
[20 Jun 2011 19:23]
Paul DuBois
Noted in 5.2.34 changelog. In the Python workbench shell, files with a nonsupported execution generated a warning and could not be run.