Benjamin Root-2 wrote > Actually, that is very telling... Did you restart python after editing > the > .py file? Python will only load a source file once in a session (unless > explicitly forced to do a reload, but that is not intended for newbies). > So, any changes to any source .py file will not take effect until you > restart your python session. This is different from other languages like > Matlab. > > Ben Root > > P.S. - The way I am able to deduce this is that when an exception occurs, > the "compiled" code will tell python which lines it came from in the > original source file so that python can display the traceback. If you > edit > the source file to add a line before the line that triggers a traceback, > it > can look like the wrong line is triggering the error because the compiled > code doesn't know that its source has been updated.
Yes, it now works for me , thanks. I didn't think a restart was necessary as I could see my '[:3]' edit in the error msg, it hadn't occurred to me that it would source the code for the error msg from the updated file even though it was out of sync with the 'compiled' version. Usjes -- View this message in context: http://matplotlib.1069221.n5.nabble.com/EMF-output-too-many-values-to-unpack-error-tp11466p39277.html Sent from the matplotlib - users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
