Can't start git in WebStorm after upgrade to MacOS Sierra - webstorm

After installing Sierra and starting WebStorm for my project, I'm getting an error that it can't find the git executable. I'm given the opportunity to 'fix it', and navigate to the file in usr/bin/git, but it won't run. In my terminal I ran which git and it returns usr/bin/git.
How can I get it started?

Same problem in Mac OS Sierra version 10.12 solved after running xcode installation with following code from terminal:
xcode-select --install

I ended up reinstalling git 2.10.0. The executable switched location to /usr/local/git/bin/git

Related

Leiningen not working MacOs Mojave due to Caused by: java.io.FileNotFoundException: Could not locate clojure/tools/nrepl/server__init.class

I am on Mojave and can't get leiningen to work.
I was using java 8, and then tried upgrading to 11 to no avail. Currently using:
openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment AdoptOpenJDK (buildb11.0.7+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.7+10, mixed mode)
I have tried copying lein to my /usr/local/bin and brew install but in both cases I get the error:
Caused by: java.io.FileNotFoundException: Could not locate clojure/tools/nrepl/server__init.class, clojure/tools/nrepl/server.clj or clojure/tools/nrepl/server.cljc on classpath.
I had a similiar problem recently on macOS Mojave (10.14.6). The following command did the trick for me:
rm -rf .lein
However, before you run this line, please make sure that...
... you are in your home directory.
... .lein is a directory associated with your leiningen installation and nothing else!
... that you have a backup of any config files, custom packages, etc. that are associated with your leiningen installation.
Once you hit enter the .lein directory will be deleted. The directory will be rebuild when you start the repl via leinigen lein repl.

C:\Windows\system32>pip install pandasFatal error in launcher: Unable to create process using '"'

I have recently installed python-2.7.14 (32-bit) on windows 10. But when I try to install any package using command pip install XXX, it gives me above error.
I tried all solution to this existing problem but it didn't work for me.
My python is installed on C:\Python27
python -m pip install XXX
worked for me but when I tried to open jupyter notebook in windows command prompt by typing
jupyter notebook
It used to give me the same Fatal error.
Actually, it was my antivirus mcafee at organisational level which was blocking the exe to run.
To solve this I had installed python in D:\ folder.

Fail to install Python 2.7.9 on a Windows google compute engine instance

I fired up a new Windows google compute engine instance. It's running Windows 2008 R2, service pack 1.
I download and try running the Python .msi installer for version 2.7.9, and it fails with this error:
There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.
I see this error for both the 64-bit and the 32-bit installer.
Has anyone else seen it or know of a work-around?
I reproduced your issue and I found two workarounds:
You can install python 2.7.6 successfully without further action.
If you need python 2.7.9 you can install it deselecting pip from the install menu.
This seems to be related to this answer in another thread although in that case the issue is with version 3.4.
Install python EXCEPT "pip"
Run the python install msi again and select "change"
Select "pip" and install the pip
It would be works...
I think it is a priority problem into the msi package...the package seems to try to install the pip before installing python.exe. So, pip can not be installed...
I'm using Windows 8.1 64-bit. I had 2.7.11 installed and then I tried to install PIP as well via Chocolatey PIP package.
I think my installation had got messed up because I had tried to install Python 3.4 as well as Python 2.
Then I had deleted all the Python 2 and Python 3 files in an attempt to get rid of this.
What worked for me was:
Editing the Environment Variables both, System and User to remove any PYTHONHOME or PYTHONPATH variables
I also deleted the path I had to python2 in the PATH environment variable
Now (as mentioned in Python Issue 22329) after deleting the Environment variables you can go into 'Programs and Features', click on the Python 2.7.11 (64-bit) program and then click 'Repair' - this then worked as I would expect without error.
Now finally I was able to go into 'Programs and Features', click on the Python 2.7.11 (64-bit) program and then click 'Uninstall'.
Edit: I assume this is connected with this PYTHON_HOME answer to a problem with Python 3.4
It seems to be a dependency issue, please try to install "Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)"

How to install pgdb on MacOS Yosemite?

On Mavericks, I downloaded the source code and and built and installed it with Distutils as I explained on Stackoverflow.
I try to reproduce it on Yosemite and I have the following error message:
Exception: pg_config tool is not available.
The command in 'setup.py' that generates the problem is supposed to "Retrieve information about installed version of PostgreSQL."
f = os.popen('pg_config --%s' % s
I used the graphic installer to install PostgreSQL on my computer.
The graphic installer did not work. By using Homebrew to install PostgreSQL, everything worked fine.
brew install postgresql

Bad Interpreter: No such file or directory error when launching iPython with Anaconda

My ipython was working fine until I installed a new IDE and accidentally changed some path settings. Now, when I try to launch ipython from terminal I get:
-bash: /Users/JohnSmith/anaconda/bin/ipython: /Users/JohnSmith/anaconda/python.app/Contents/MacOS/python: bad interpreter: No such file or directory
How do I change my path/local environment settings back so that it works?
It seems that uninstalling and re-installing Anaconda was the easiest solution (after several hours of playing around with my PATH variables, etc).
This github thread shows the solution from spyder dev ccordoba12:
https://github.com/spyder-ide/spyder/issues/9951#issuecomment-517913824
run
conda install -f python.app
(Very fast to run)
Then spyder etc. was fixed. Apparently an incorrect python path in the launch script.
FYI I had this same issue with Anaconda install with python 3.8 (2022), after a big mess with upgrading anaconda via conda update --all. On MacBook Pro (Intel)