2009/12/31 Fernando Perez fperez@gmail.com:
On Thu, Dec 31, 2009 at 4:54 AM, Darren Dale dsdal...@gmail.com wrote:
I have been resistant to committing this patch because (in my opinion)
mpl should not have to provide workarounds for bugs in package X on OS
Y, distribution Z. I think this
Howdy,
On Sat, Nov 7, 2009 at 12:30 PM, Darren Dale dsdal...@gmail.com wrote:
Me too. And thank you for posting the report and a workaround.
Quick question: would it be worth adding this monkeypatch to mpl
proper? Right now, the qt4 backend is effectively unusable out of the
box in distros
On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut cont...@pythonxy.com wrote:
A simpler fix would be:
? ? ? ?class FigureWindow(QtGui.QMainWindow):
? ? ? ? ? ?def __init__(self):
? ? ? ? ? ? ? ?super(FigureWindow, self).__init__()
? ? ? ? ? ?def closeEvent(self, event):
? ? ? ?
On Sat, Nov 7, 2009 at 9:53 AM, Pierre Raybaut cont...@pythonxy.com wrote:
On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut cont...@pythonxy.com
wrote:
A simpler fix would be:
? ? ? ?class FigureWindow(QtGui.QMainWindow):
? ? ? ? ? ?def __init__(self):
? ? ? ? ? ? ?
Hi,
Some Spyder users have reported a critical bug occuring with matplotlib
0.99's Qt4 backend and PyQt4 v4.6 (e.g. in Ubuntu Karmic).
Here is the traceback after calling 'plot([])', closing figure and
calling again 'plot([])' (e.g. in an IPython session with options
--pylab and --q4thread):
A simpler fix would be:
class FigureWindow(QtGui.QMainWindow):
def __init__(self):
super(FigureWindow, self).__init__()
def closeEvent(self, event):
super(FigureWindow, self).closeEvent(event)
