Continous Python console pop up after installing Pycharm 4.0.1 - python-2.7

I recently updated to Pycharm 4 and all of a sudden, am gettin these crazy console pop ups whenever I launch Pycharm,run an app,or even press any button that fires any sort of event in the editor.
I have unchecked the Use IPython if available option in both the settings and in the default settings menus, restarted Pycharm with no luck. How do i solve this problem? Can i uninstall IPython?

Related

Unable to uninstall VMWare Work Station on Windows 8.1

I am facing an issue. When I try to uninstall VMWare,the following message is shown.
The MSI failed message. Even though I search in google and I didn't find a way to solve.
VMWare version was
Have you tried uninstalling it using elevated rights?
Try this:
Right click on your start button and select "Command Prompt (Admin)".
In the command prompt, type "control appwiz.cpl".
The old style uninstall screen should open, so you can select "VMWare Player" from the list, then at the top, select "Change"
In the pop up window, choose "Uninstall"

How to isolate terminal on WebStorm 2019.3

In WebStorm 2018.3.5 when I press Up key it suggests me the last command I ran on this exact tab.
On WebStorm 2019.3.1 when I run a command on other tab or run something from system terminal and open a new tab and press Up it suggests me the last actual command ran on the system not in current tab.
Is there any way to configure it to have its own commands history in the latest WebStorm version?
OS I am currently running is Linux Mint 18 and using zsh as a shell.
Thanks.

Degugging a react native / expo app with webstorm

I can't debug my react native / expo app in WebStorm, but I can in Visual Studio Code.
I have a react native app that I can successfully run using expo. I set up the configuration according to the info on this site:
https://blog.jetbrains.com/webstorm/2018/02/webstorm-2018-1-eap-181-3263/#debugging-expo
When I click "run" or "debug" and "Debug JS Remotely" is turned off, the bundler builds a JS bundle and the app starts on my devices.
But once I turn on "Debug JS Remotely", the bundler only says:
Starting custom debugger by executing: : [my working directory] [my working directory again]
and never goes on to build the JS bundle.
After a short while, a red screen appears on the device, and it says:
Unable to connect with remote debugger
Timeout while connecting to remote debugger
onFailure
DevSupportManagerImpl.java:851
onFailure
WebsocketJavaScriptExecutor.java:83
run
WebsocketJavaScriptExecutor.java:142
handleCallback
Handler.java:790
dispatchMessage
Handler.java:99
...
The bundler doesn't say anything more than the message above.
As soon as I turn off remote debugging, the the bundler starts building again and finishes with
"Building JavaScript bundle: finished in ...ms"
as usual, but the device, again, shows the red screen with aforementioned messages, or doesn't show anything but the regular white screen with a message at the bottom saying "Downlading JavaScript bundle 100,00%". I either have to stop and restart within WebStorm or I have to close the expo app and re-open it. Either way will make the app start again on my device.
This is my first time working with javascript, react native, expo, so I am not sure, but it should be possible to debug in WebStorm directly, right? As mentioned, in Visual Studio Code everything including debugging works fine, so I don't think it's anything in the code. Maybe someone here has an idea where the problem lies?
node -v: v11.6.0
react-native -v: react-native-cli: 2.0.1, react-native: 0.57.1
Any help will be greatly appreciated! Thanks in advance!
PROOF
HOWTO
Looks like there's been an update to how you can setup Configurations since you tried.
Try changing the Bundler host to 127.0.0.1 and try again.
I just setup Webstorm v2020.2 yesterday to debug my Expo application and it is working as expected.
These instructions were all that I required: https://www.jetbrains.com/help/webstorm/react-native.html#ws_react_native_create_run_config
On the main menu, go to Run | Edit Configurations, click icons.general.add.svg and select React Native from the list. The Run/Debug Configuration: React Native opens.
Choose whether you want WebStorm to build and launch the application for you:
Select the Build and launch checkbox if you are launching your application for the first time or if you have updated its native code since the last run.
If your application uses Expo, clear the checkbox because this bundler takes care of the process itself.
If you selected the Build and launch checkbox, choose the target platform, Android or iOS. Depending on your choice, WebStorm will run the bundler with react-native run-ios or with react-native run-android.
Optionally, type the arguments to be passed to React Native, for example, specify the simulator type through the ‑‑simulator flag: ‑‑simulator="iPhone 4s".
In the Bundler host field, specify the host where the React Native bundler runs, the default value is localhost.
If you are using Expo, change the default bundler host to ensure successful connection with the debugger. This connection may fail because WebStorm by default uses localhost to start debugging while Expo expects 127.0.0.1 or an external IP address depending on what is selected in Connection field of the Metro bundler configuration. See Debugging a React Native application that uses Expo for details.
In the Bundler port field, specify the port on which the React Native bundler runs, by default 8081 is chosen, learn more from the React Native official website.
Choose the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux.
Specify the path to react-native-cli and the working directory of the application. Optionally, type the environment variables for react-native run-android or react-native run-ios.
By default, WebStorm starts the React Native bundler automatically when you invoke the run/debug configuration. If you have already started the bundler from outside WebStorm, for example, from the command line, you can re-use it without stopping and restarting. Select your bundler in the Before Launch area and click Remove.
The issue is tracked at WEB-35719, please follow it for updates

Unable to install Docker for Windows for the Divio App

When trying to set up the Divio app, I get this warning screen.
DivioSetupWarningScreen
However, even though the picture claims I do, I don't have Docker Toolbox installed. When I try to install Docker for Windows on anyways by pressing the "Continue" button as seen in the picture above, I get this.
DockerNotInstalled
In the second picture, I tried clicking "Contact Support," but that led me to a blank webpage. Also, if I try to install Docker Windows without the Divio App, but it would not let me because I do not have the enterprise Windows OS, just the home. I also tried downloading Boot2Docker Start, but that didn't really help.
I'm at a loss as to what to try next. Any help would be appreciated.Thanks!
As you have Windows Home edition, one of the solutions would be to install Docker Toolbox/VirtualBox manually and use Divio CLI in PowerShell. Because current version of Divio App does not recognize Windows edition type. It should be presented in the next coming release.

Run Configuration in eclipse

Hi I'm sure this is a stupid question but I am running eclipse in linux mint 15 and whenever I try to press the main run option in the upper tab of the eclipse menu (next to the build option) I get a message saying systemtap is not installed, and then the run button grays out and I cant use it unless I restart eclipse and run into the same problem. I know this is an issue with the run configuration but when I attempt to alter it in the run configurations menu all that ends up happening is a run button being created in the favorites tab for the particular project I have selected. What I am trying to do is have the main run button launch whichever project I have selected through the default option instead of attempting to automatically use systemtap. Thanks
You simply need to install the systemtap packages. From a terminal...
sudo apt-get install systemtap