Lewis Levin | 14 Jul 17:12 2014
Picon

Also: preferences crashes immediately

This also appears to be a PySide binding problem.   If PyQT is required then I probably won't use Spyder.  The PYQT install process is too burdensome, requiring a binary installer or build from source.   Pyside installs as pip install PySide.  Seems like the right thing.


Note that "ipython qtconsole" works on my system so seems like qt and Pyside work with ipython.

This is an excerpt of the crash dump:

Process:         Python [714]
Path:            /Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier:      org.python.python
Version:         2.7.8 (2.7.8)
Code Type:       X86-64 (Native)
Parent Process:  bash [589]
Responsible:     Terminal [586]
User ID:         501

Date/Time:       2014-07-14 08:09:54.214 -0700
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version:  11
Anonymous UUID:  7DEC5AA2-A823-E9A8-A154-F0DC5E3DC395


Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT

Application Specific Information:
Performing <at> selector(qtDispatcherToQAction:) from sender NSMenuItem 0x1072e7b00

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtCore                         0x00000001066c98f1 QVariant::~QVariant() + 17
1   libpyside-python2.7.1.2.dylib 0x00000001061b577a PySide::MetaFunction::call(QObject*, int, _object*, _object**) + 1466
2   libpyside-python2.7.1.2.dylib 0x00000001061af5ed PySide::SignalManager::emitSignal(QObject*, char const*, _object*) + 157
3   QtCore.so                     0x0000000105f3b1a7 Sbk_QObjectFunc_emit + 279
4   org.python.python             0x00000001000c2f7d PyEval_EvalFrameEx + 21485
5   org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
6   org.python.python             0x000000010003e990 function_call + 176
7   org.python.python             0x000000010000cde2 PyObject_Call + 98
8   org.python.python             0x00000001000bc8c7 PyEval_CallObjectWithKeywords + 87
9   libpyside-python2.7.1.2.dylib 0x00000001061baa45 PySide::Property::setValue(PySideProperty*, _object*, _object*) + 69
10  QtCore.so                     0x0000000105f3a34f Sbk_QObject_setattro + 47
11  org.python.python             0x000000010005bd15 PyObject_SetAttr + 133
12  org.python.python             0x00000001000beda6 PyEval_EvalFrameEx + 4630
13  org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
14  org.python.python             0x000000010003e990 function_call + 176
15  org.python.python             0x000000010000cde2 PyObject_Call + 98
16  org.python.python             0x000000010001f43d instancemethod_call + 365
17  org.python.python             0x000000010000cde2 PyObject_Call + 98
18  org.python.python             0x00000001000bc8c7 PyEval_CallObjectWithKeywords + 87
19  libpyside-python2.7.1.2.dylib 0x00000001061afcd5 PySide::SignalManager::callPythonMetaMethod(QMetaMethod const&, void**, _object*, bool) + 581
20  libpyside-python2.7.1.2.dylib 0x00000001061af8f7 PySide::SignalManager::qt_metacall(QObject*, QMetaObject::Call, int, void**) + 695
21  QtCore                         0x000000010635c950 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1952
22  QtGui                         0x000000010870dbe8 QLineEdit::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 94
23  QtCore                         0x000000010635ca0f QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2143
24  QtGui                         0x0000000108900d52 QLineControl::textChanged(QString const&) + 56
25  QtGui                         0x000000010870f544 QLineControl::finishChange(int, bool, bool) + 382
26  QtGui                         0x000000010870ff39 QLineControl::internalSetText(QString const&, int, bool) + 465
27  QtGui.so                       0x00000001078e6de5 Sbk_QLineEditFunc_setText + 165
28  org.python.python             0x00000001000c39e0 PyEval_EvalFrameEx + 24144
29  org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
30  org.python.python             0x00000001000c33c0 PyEval_EvalFrameEx + 22576
31  org.python.python             0x00000001000c3bcf PyEval_EvalFrameEx + 24639
32  org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
33  org.python.python             0x000000010003e990 function_call + 176
34  org.python.python             0x000000010000cde2 PyObject_Call + 98
35  org.python.python             0x000000010001f43d instancemethod_call + 365
36  org.python.python             0x000000010000cde2 PyObject_Call + 98
37  org.python.python             0x00000001000bc8c7 PyEval_CallObjectWithKeywords + 87
38  libpyside-python2.7.1.2.dylib 0x00000001061afcd5 PySide::SignalManager::callPythonMetaMethod(QMetaMethod const&, void**, _object*, bool) + 581
39  libpyside-python2.7.1.2.dylib 0x00000001061af8f7 PySide::SignalManager::qt_metacall(QObject*, QMetaObject::Call, int, void**) + 695
40  QtCore                         0x000000010635c950 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1952
41  QtGui                         0x00000001083d070e QAction::activate(QAction::ActionEvent) + 224
42  QtGui                         0x000000010838e29e -[QCocoaMenuLoader qtDispatcherToQAction:] + 65
43  com.apple.AppKit               0x00007fff8c055260 -[NSApplication sendAction:to:from:] + 327
44  com.apple.AppKit               0x00007fff8c0701c8 -[NSMenuItem _corePerformAction] + 394
45  com.apple.AppKit               0x00007fff8c06ff04 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 117
46  com.apple.AppKit               0x00007fff8c0bf40d -[NSMenu _internalPerformActionForItemAtIndex:] + 35
47  com.apple.AppKit               0x00007fff8c0bf289 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 104
48  com.apple.AppKit               0x00007fff8c065ff6 NSSLMMenuEventHandler + 716
49  com.apple.HIToolbox           0x00007fff8e30a1d4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 892
50  com.apple.HIToolbox           0x00007fff8e309787 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 385
51  com.apple.HIToolbox           0x00007fff8e31d880 SendEventToEventTarget + 40
52  com.apple.HIToolbox           0x00007fff8e353640 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 420
53  com.apple.HIToolbox           0x00007fff8e386228 SendMenuCommandWithContextAndModifiers + 59
54  com.apple.HIToolbox           0x00007fff8e3861d0 SendMenuItemSelectedEvent + 178
55  com.apple.HIToolbox           0x00007fff8e3860af FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 94
56  com.apple.HIToolbox           0x00007fff8e38e085 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 718
57  com.apple.HIToolbox           0x00007fff8e38dcb1 _HandleMenuSelection2 + 446
58  com.apple.AppKit               0x00007fff8bfd862c _NSHandleCarbonMenuEvent + 284
59  com.apple.AppKit               0x00007fff8be3752e _DPSNextEvent + 2170
60  com.apple.AppKit               0x00007fff8be3689b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
61  com.apple.AppKit               0x00007fff8be2a99c -[NSApplication run] + 553
62  QtGui                         0x0000000108396037 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 519
63  QtCore                         0x00000001063466e7 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 79
64  QtCore                         0x000000010634684a QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 346
65  QtCore                         0x00000001063494f9 QCoreApplication::exec() + 199
66  QtGui.so                       0x000000010769bd39 Sbk_QApplicationFunc_exec_ + 41
67  org.python.python             0x00000001000c2dc2 PyEval_EvalFrameEx + 21042
68  org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
69  org.python.python             0x00000001000c33c0 PyEval_EvalFrameEx + 22576
70  org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
71  org.python.python             0x00000001000c33c0 PyEval_EvalFrameEx + 22576
72  org.python.python             0x00000001000c3bcf PyEval_EvalFrameEx + 24639
73  org.python.python             0x00000001000c4f93 PyEval_EvalCodeEx + 2115
74  org.python.python             0x00000001000c50b6 PyEval_EvalCode + 54
75  org.python.python             0x00000001000e993e PyRun_FileExFlags + 174
76  org.python.python             0x00000001000e9bda PyRun_SimpleFileExFlags + 458
77  org.python.python             0x0000000100100bfd Py_Main + 3101
78  org.python.python             0x0000000100000f14 0x100000000 + 3860

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Lewis Levin | 14 Jul 17:07 2014
Picon

Possible problem with PySide bindings and matplotlib

Not sure I can interpret this error message from the internal console (of the new 2.3):

>>> Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/spyderlib/spyder.py", line 1587, in hideEvent
    QMainWindow.hideEvent(self, event)
TypeError: 'PySide.QtGui.QWidget.hideEvent' called with wrong argument types:
  PySide.QtGui.QWidget.hideEvent(PySide.QtCore.QEvent)
Supported signatures:
  PySide.QtGui.QWidget.hideEvent(PySide.QtGui.QHideEvent)

The code runs, the figure window opens.  Nothing is drawn in the figure window.  The figure window hangs.

Note that this code runs as is in a stand-alone ipython window and in python run from terminal (OS X Mavericks).

Note that when I try to open an ipython console in Spyder, that tool windows "hangs"  by which I mean that "connecting to kernel" runs with spinning circle forever.

My ipython runs from terminal fine and from other ides.  Probably a config problem and I am clueless to diagnose such problems.

Thanks,
Lewis

Note that Spyder was installed as pip install -U spyder on Python 2.7.7.

(trying to come back to Spyder)

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Sheila the angel | 14 Jul 14:07 2014
Picon

separate the console

Hello All,
Is it possible to separate the Ipython console in Spyder from the main windows.
I can move the console at different positions in Spyder window but can't use it as separate/de-attached windows.
Thanks

--
Sheila  


--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Gufran Pathan | 14 Jul 14:21 2014
Picon

Redirect Output to File

Hi,

Is there a way in Spyder through which I can redirect the output on the console to a file (when running a .py file, either in the interactive console or a dedicated one)? I can do this in PyDev, but can't figure out how to do it in Spyder.

Thanks!

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Evan Carter | 13 Jul 04:40 2014
Picon

Using the User Module Deleter with classes that have a __del__ method

If I write a module called testclass containing this:

import time
class TestClass(object):
    def __init__(self):
        self._createtime = time.strftime('%H:%M:%S', time.localtime()) 
        print "In __init__ at {} 'time' is bound to {}".format(self._createtime, time)
    def __del__(self):
        print "in __del__ for TestClass instance created at {} time is bound to {}".format(self._createtime, time)

And create another file, call it testmain.py, that consists of this:

import testclass

tc = testclass.TestClass()


The first time I run testmain.py from the Spyder console I get the intuitive result:
>>> runfile('/Users/evan/Desktop/testmain.py', wdir=r'/Users/evan/Desktop')
In __init__ at 22:09:14 'time' is bound to <module 'time' from '/Users/evan/anaconda/python.app/Contents/lib/python2.7/lib-dynload/time.so'>

But the second time I get weird behavior because the original module object has been killed by the UMD, so (for example) the original import of the time module is gone:
>>> runfile('/Users/evan/Desktop/testmain.py', wdir=r'/Users/evan/Desktop')
UMD has deleted: testclass
In __init__ at 22:09:15 'time' is bound to <module 'time' from '/Users/evan/anaconda/python.app/Contents/lib/python2.7/lib-dynload/time.so'>
in __del__ for TestClass instance created at 22:09:14 time is bound to None
If I were doing real work in __del__ then this would pose a problem

I've come up with three solutions:
  1. Don't use the UMD with classes that have __del__ methods. This works fine, but I lose out on the UMD
  2. Clean up after myself: call "del tc" at the end of testmain.py. This doesn't work so well. Not only am I stuck managing my own memory, but while I'm doing development is totally possible that my code will hit an error before I hit the "del tc" line. I can stick "del tc" in a finally block, but then I'm really doing manual memory management.
  3. Have the __del__ method actually check whether its context has already been cleaned up ("if time is None: ...") and if so vary its behavior appropriately. Not suitable for all applications.
Is there a better workaround out there?

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Picon

Run another python version on console.


Hi!!!

I'm trying to change my version of python on the console of spyder. I mean, i downloaded spyder and it only let me run the code on python or ipython, but the oldest version, see the image "Problemas con spyder".


But in my shell y run the python 2.7.7 with anaconda. See image "Problema spyder con anadonda" .





I really want to change the interpreter to my python 2.7.7 with anaconda.

Please save me






--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Carlos Córdoba | 11 Jul 02:56 2014
Picon

ANN: Spyder v2.3 is released!

Hi all,

On the behalf of Spyder's development team (http://code.google.com/p/spyderlib/people/list), I'm pleased to announce that Spyder 2.3 has been released and is available for Windows XP/Vista/7/8, GNU/Linux and MacOS X: https://bitbucket.org/spyder-ide/spyderlib/downloads

This release represents 14 months of development since version 2.2 and introduces major enhancements and new features:

   * Python 3 support (versions 3.2, 3.3 and 3.4 are supported).
   * Various Editor improvements:
     - Use the Tab key to do code completions
     - Highlight cells
     - First-class support for Enaml files
     - Improve how calltips are shown
   * Better looking Object Inspector
   * Several refinements to the user interface to make it easier and more intuitive
   * And many other changes: http://code.google.com/p/spyderlib/wiki/ChangeLog

Spyder 2.2 has been a huge success (being downloaded more than 400,000 times) and we hope 2.3 will be as successful as it. For that we merged 30 pull requests from 11 authors, and added almost 1000 commits between these two releases.

Spyder is a free, open-source (MIT license) interactive development environment for the Python language with advanced editing, interactive testing, debugging and introspection features. Originally designed to provide MATLAB-like features (integrated help, interactive console, variable explorer with GUI-based editors for dictionaries, NumPy arrays, ...), it is strongly oriented towards scientific computing and software development. Thanks to the `spyderlib` library, Spyder also provides powerful ready-to-use widgets: embedded Python console (example: http://packages.python.org/guiqwt/_images/sift3.png), NumPy array editor (example: http://packages.python.org/guiqwt/_images/sift2.png), dictionary editor, source code editor, etc.

Description of key features with tasty screenshots can be found at:
http://code.google.com/p/spyderlib/wiki/Features

Don't forget to follow Spyder updates/news:
  * on the project website: http://code.google.com/p/spyderlib/
  * and on our official blog: http://spyder-ide.blogspot.com/

Last, but not least, we welcome any contribution that helps making Spyder an efficient scientific development/computing environment. Join us to help creating your favorite environment!
(http://code.google.com/p/spyderlib/wiki/NoteForContributors)

Enjoy!
-Carlos

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.

Piotr Bentkowski | 9 Jul 15:42 2014
Picon

More space for typing command line options in Run Settings

Could we have more space, than just one short line, for typing command line options in Run Settings (F6)? More like a text area maybe. Going full screen does not help much when you have to type three long directory paths (e.g. where input data are, where results should go, where error message should go...). I love Spyder for prototyping my scripts before sending then on a cluster computer.
Thanks for the awesome work!

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
anatoly techtonik | 3 Jul 11:55 2014
Picon

Dropping support for PyQt4 API #1

Are there any objections against dropping support for PyQt4 API #1? Both PySide and Python 3 are
compatible with API #2 only. API #1 will still be supported in 2.3, but the question is if anybody
still use it? Note that Spyder with IPython always uses API #2.

I've made a pull request that removes import hacks that we maintain for this compatibility:
https://bitbucket.org/spyder-ide/spyderlib/pull-request/53/switch-to-pyqt4-api-2-and-remove-ipython/diff
Feel free to test it.

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
Rothrock | 1 Jul 05:24 2014
Picon

.temp.py

Running spyder 2.2.5 on Mavericks. Every time I start Spyder I get a file .temp2.py open in the editor. It tells me 

# -*- coding: utf-8 -*-

"""

Spyder Editor


This temporary script file is located here:

/Users/rothrock/.spyder2/.temp.py

"""


I've gone in and renamed the file. If I close .temp.py before closing spyder and rename it using terminal then I get a new .temp.py generated when I open spyder. If I leave it open, quit spyder and then rename .temp.py I get an error the next time I open spyder:


Spyder 2.2.5 internal shell on Python 2.7.5 64bits [Darwin]

Inspect Spyder internals:

  spy.app, spy.window, dir(spy)

>>> Traceback (most recent call last):

  File "/Applications/Spyder.app/Contents/Resources/lib/python2.7/spyderlib/plugins/editor.py", line 505, in restore_scrollbar_position

    self.get_current_editor().centerCursor()

AttributeError: 'NoneType' object has no attribute 'centerCursor'


How can I get rid of .temp.py and not have an error when I start up spyder?

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
SixString | 27 Jun 23:27 2014

Please bring back "Open an IPython console at startup" preference

I have been using Spyder v2.3.0beta2, and I recently installed Anaconda that includes Spyder v2.3.0rc.  What I miss in the rc version is the preference "Open an IPython console at startup".  I don't care what the default value for this preference is, but I prefer to disable this option to speed up opening Spyder and to save a few clicks to get to the Python console.  My firewall logs shows that the IPython console makes a lot of local host connections.

Thanks for your consideration.

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to spyderlib-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.

Gmane