spyder 3.x closing parenthesis hangs when heavy data in memory - spyder

I am working with lots of Pandas dataframe and dictionaries in memory, i realise the more data there is, the more Spyder will hang when you type closing parenthesis the the console.
Does anyone know how to fix this? i already disable most options.

(Spyder maintainer here) Please go to the menu
Tools > Preferences > IPython console > Display
and deactivate the option called Display ballon tips.

Related

how to disable the help information when we hover the cursor on a variable/function in spyder [duplicate]

not sure where to ask:
is there a way to not have the help tooltip/popup/hover window opening in spyder?
since updating to 4.0 the window does not close when you change between windows:
guess something like this will be reported and delt with in future updates but for now i would be happy to just disable it
(using 64-bit windows-10 machine)
(Spyder maintainer here) Yes, there is. You need to go to the menu
Tools > Preferences > Completion and linting > Introspection
and deactivate the option called Enable hover hints.
Note: The issue you posted above with the hover not hiding when giving focus to other applications will be fixed in our next bugfix version (4.1), to be released in a couple of months.

How to disable automatic function docstring generation in Spyder?

Spyder (the Python IDE) generates a function docstring automatically when you click Enter after the first line of the function def. How can one disable this feature?
I've looked around in Tools (for instance in Tools -> Preferences -> Editor) and did not find a way to do it. But there are tons of features in Spyder so maybe I'm missing it.
Are you using an anaconda install with kited running in the background? Opening task manager and stopping this from running fixed the problem for me.
Edit: This may be incorrect
When you type in the triple quotes, an icon will pop up that says Generate docstring. When this happens, do not hit Enter. Just hit esc.
Until we can just deactivate it in settings, that's what I've been doing.

ZeroBrane - how to clear debug window?

I wonder if there is a way to clear the "local console" pane in ZeroBrane. Sometimes it gets "clogged" with no way to clean it - for example checking _G produces massive amount of text and everything slows to halt afterwards.
I am using v0.50 that came bundled with Marmalade, if that matters. I tried local menu (right-click) but there is nothing.
You can use clear command (simply type clear and Enter), which will clear the console content (it's described in the introductory text at the top of the console window).
I suggest you upgrade to a newer version as 0.50 is quite old.

Saving Python code in Anaconda

I am having problems saving the Python code in Anaconda. I write code, Go to File Save as the file is saved but when I open it is empty, no code. I read that IDLE does not save code, it erases it when I close Anaconda.
I have searched in books, youtube tutorials and nothing. I could not find this topic. I can find advanced topics, but this one no.
Thank you for your help!
Best,
Tiberiu
This somewhat depends on what OS you are on. I can speak from my experience. I would highly recommend using PyCharm as an IDE.
But more fundamentally than that, lets talk about saving files. On Mac OS X or Ubuntu 14.04 (or the like), lets say you want to create a python file. One way is to do the following in a terminal:
nano hello.py
This opens up a text editor whose instructions for use are on the bottom of the screen. On Windows you could do:
notepad hello.py
In both cases you then write your code. Lets say the content was:
#content of hello.py
print "Hello World!"
Then you need to save the file and execute it with Python.
Which brings us to the Python issue.
Once you have installed Anaconda, and assuming that there are no other Python installations on your computer. The Anaconda Python should be the active Python on system.
Suffice to say that there are other ways of saving files rather than using IDLE. Personally I have found PyCharm to be a much better IDE for writing Python code.
To address the IDLE issue more directly once you type in the terminal/command prompt idle to launch an IDLE session, likely the IDLE Shell will open up. Perhaps you are trying to save this, in which case you will only save the Shell session.
So go to File - New - Save. This should work without any problem (it does on my system). Good luck! Hope this helps.

Force Open Lua Console or Run Lua Console Automatically on Startup

I'm new to Wireshark & Lua and I have a question that I can't seem to find the answer to by reading around online
Is there a way to open the Wireshark Lua console window on start up? Or even automatically open dialogs created by listeners on start up? I was hoping there were some commands or capability that would allow me to open (not just create) dialogs from within a script.
I've read about the exploit for the console in versions 1.6 and earlier, but I'm running 1.6.8 and I'd rather not use something that could potentially cause Wireshark to be unstable.
Modify the bottom of C:\Program Files\Wireshark\console.lua. Before the final "end", add:
run_console()
You can find an advanced option in the preferences dialog:
Open Preferences from the Edit menu
Navigate to Advanced
Filter for console
Change the value for gui.console_open to ALWAYS

Resources