This might happen to any one, because we are humans and we often tend to make some stupid mistakes for which we do regret later. But this does have a small solution to undo the problem. You can reset the $PATH variable to the default position. Let me first tell you what happens if you remove the existing path from the $PATH variable. One cannot use any of the commands in the terminal. Simple commands like open, clear, vim, touch nothing works. You cannot access the development packages through the terminal like python interpreter, java, gcc. Without these basic commands, a developer cannot survive. So, always be careful when you are going to edit your $PATH variable so that you don’t face any problems in the future. bash_profile or /.profile file, you might have used the text editor like TextEdit or emacs or any other editor. Open Terminal and run the command source ~/.bash_profile which will make the changes immediately.Ĭheck the $PATH variable’s value by running echo $PATH. It should flash the /usr/bin:/usr/sbin:/bin:/sbin So, go to the application which you have used to edit the above files and go to file menu and open the /.bash_profile or /.profile file from the recent menu.Īfter opening it, reset the path to its default by typing export PATH=/usr/bin:/usr/sbin:/bin:/sbin and save the file. To confirm that your path has been reset properly. Type in the basic commands and check if they are working properly. Note: Do not put any quotes around the path while you are editing it in the text editor.
This is one issue which I was facing on Mac OSX Mavericks 10.9.4.
Later, if you type in one more line of code say > print ‘World’ When you open the python interpreter in the terminal, executing two lines of code one after the other will give you an segmentation fault: 11 and the python interpreter closes.įor instance: > print ‘Hello’ gives you the output as Hello #ADOBE READER FOR IMAC 10.8.2 MAC OSX#
This was issue for both Python 2.7.6 version and Python 3.3.3 The interpreter exists with an segmentation fault : 11 though there is nothing wrong with the code.
This is a bug in the readline compatibility in python, related to changes introduced in OSX10.9.
0 kommentar(er)
