The native features in MATLAB are often very good most of the time, as I’ve yet to hear anybody spending time to shop for a IDE outside the official one.<\/p>\n\n\n\n
Atom has the feel of Maple\/MathCAD, and Jupyter Notebook has the feel of Mathematica. Spyder feels like MATLAB the most, but it’s hugely primitive.<\/p>\n\n\n\n
IDLE is more miserable than a command prompt. It doesn’t even have the decency to recall command history with up arrow. It’s like freaking DOS before loading doskey.com. Not to mention that single clicking on the window won’t set the cursor to the active command line, which you have to scroll all the way down to click on the bottom line. WTF! I’d rather use the command prompt and give up meaningless syntax coloring.<\/p>\n\n\n\n
IPython (in Spyder) is unbearably slow (compare to MATLAB’s editor which I consider slow to the extent that it’s marginally bearable for the interactive features it offers), but at least usable unlike IDLE, and most importantly the output display is pprint (pretty printer) formatted so it’s legible. Just type locals() and see what kind of sh*t Python spits out in IDLE\/cmd.exe and you’ll see what I meant.<\/p>\n\n\n\n
I simply cannot live without However, pretty printer doesn’t even come close to MATLAB in terms of the amount of dirty work ` did to format the text to make it easy to read. Keys in the dictionary shown in pretty printer in Python are not right-aligned like MATLAB struct so we can easily tell keys and values apart. For example:<\/p>\n\n\n\n I often convert things to MATLAB who<\/code>\/whos<\/code> provided in IPython, but I still don’t like it showing the accessible functions\/modules along with the variables (I know, Python doesn’t tell them apart). Nonetheless it’s still weak because these are automagics that doesn’t return the results as Python data (just print). Spyder’s ‘variable explorer’ is the only place I can find that doesn’t include loaded functions\/modules. Python should have provided facilities to get the user-introduced variables exclusively and leave the modules to a different function like MATLAB’s import<\/code> command that shows imported packages\/classes.<\/p>\n\n\n\nMATLAB struct shows:\n name: 'S'\n size: [9 1]\n bytes: 7765\n class: 'struct'\n global: 0\n sparse: 0\n complex: 0\n nesting: [1\u00d71 struct]\n persistent: 0\n\nPython with Pretty Printer shows:\n{'__name__': '__main__',\n '__doc__': 'Automatically created module for IPython interactive environment',\n '__package__': None,\n '__loader__': None,\n '__spec__': None,\n '__builtin__': <module 'builtins' (built-in)>,\n '__builtins__': <module 'builtins' (built-in)>,\n '_ih': ['', 'locals()'],\n '_oh': {},\n '_dh': ['C:\\\\Users\\\\Administrator'],\n 'In': ['', 'locals()'],\n 'Out': {},\n 'get_ipython': <bound method InteractiveShell.get_ipython of <ipykernel.zmqshell.ZMQInteractiveShell object at 0x00000000059B7828>>,\n 'exit': <IPython.core.autocall.ZMQExitAutocall at 0x5a3b198>,\n 'quit': <IPython.core.autocall.ZMQExitAutocall at 0x5a3b198>,\n '_': '',\n '__': '',\n '___': '',\n '_i': '',\n '_ii': '',\n '_iii': '',\n '_i1': 'locals()'}<\/pre>\n\n\n\ndataset()<\/code> because the disp()<\/code> method is excellent, such as struct2dataset(ver())<\/code>. table\/disp()<\/code> is nice, but I think they overdid it by defaulting to fancy rich-text that bold the header, which makes it a magnitude of orders slower, and it’s not using the limited visual space effectively to show more data. Python still has a lot more to do in the user-friendly department.<\/p>\n