search

thegooglecodearchive / editra-plugins

Automatically exported from code.google.com/p/editra-plugins
0 stars 1 forks source link

PyExpressions Crash #175

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Received via error reporter:

started Editra, viewed shelf, added launch, PyDebug, PyVariable, PyExpression. 
Ran a short demo program I wrote to sort lists with a lambda key, nothing too 
extreme here, and when I clicked on the "+" sign in PyExpression to add an 
expression, I got the error below.

#---- System Information ----#
Editra Version: 0.6.48
Operating System: Windows NT 6.1 (build 7601, Service Pack 1)
Python Version: 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit 
(Intel)]
wxPython Version: 2.8.12.0 (msw-unicode)
wxPython Info: (__WXMSW__, wxMSW, unicode, wx-assertions-on, SWIG-1.3.29)
Python Encoding: Default=ascii  File=mbcs
wxPython Encoding: cp1252
System Architecture: 32bit x86
Byte order: little
Frozen: windows_exe
#---- End System Information ----#

#---- Traceback Info ----#
*** Mon May 23 11:19:32 2011 ***

Traceback (most recent call last):
 File "c:\users\bsoher\appdata\roaming\editra\plugins\pystudio-0.1-py2.6.egg\PyStudio\Debugger\ExpressionsShelfWindow.py", line 117, in OnButton
 File "c:\users\bsoher\appdata\roaming\editra\plugins\pystudio-0.1-py2.6.egg\PyStudio\Debugger\ExpressionsShelfWindow.py", line 95, in SetExpression
TypeError: 'NoneType' object does not support item assignment

Original issue reported on code.google.com by CodyPrec...@gmail.com on 23 May 2011 at 3:28

GoogleCodeExporter commented 9 years ago

Original comment by CodyPrec...@gmail.com on 23 May 2011 at 3:36

GoogleCodeExporter commented 9 years ago 
So far I haven't been able to replicate this error. Need more information.

Original comment by rans1...@gmail.com on 24 May 2011 at 8:43

GoogleCodeExporter commented 9 years ago 
Couldn't reproduce it either but from the traceback it was obvious that the 
cause was from 'self.expressions' being initialized from non existent profile 
data so it was assigned None instead of {}.

Fixed in current svn

Original comment by CodyPrec...@gmail.com on 24 May 2011 at 3:17