can't run py files from atom after uninstalling old python










0















I had been able to run python files via Atom's Open in Browser, but now that I have uninstalled python 2.7 (still have the latest version installed) it throws an error saying I have no program associated with that file type. Any help would be appreciated!










share|improve this question






















  • A few questions which may help. Are you using the script package ? Have you tried re-installing the Open in Browser package ? Do you run atom from the command line ? When you try to run your python file, do you call python or python3 ?

    – Patol75
    Nov 15 '18 at 4:41











  • Thanks for the reply. I have script installed but it doesn't seem to work properly so I don't use it. I just tried re-installing Open in Browser, but the the issue persists. I don't run atom from the command line; I just open it like a normal program and load in project folders. I reinstalled python on my home comp and that solved the issue, but the problem persists on my work laptop after trying all of the provided solutions.

    – Matt
    Nov 15 '18 at 22:16












  • I run my scripts with script. There are two things I do. First, in the settings of script, I specify that the folder from which the script command needs to be called is the one of the current file. And second, I specify in the launching options (Ctrl + Shift + Alt + O) that the command to execute is python3. This works for me. Another question which may help: what command do you call in the terminal to use python? Because if it is python3 and that atom expects python, then that is maybe the problem.

    – Patol75
    Nov 15 '18 at 23:59
















0















I had been able to run python files via Atom's Open in Browser, but now that I have uninstalled python 2.7 (still have the latest version installed) it throws an error saying I have no program associated with that file type. Any help would be appreciated!










share|improve this question






















  • A few questions which may help. Are you using the script package ? Have you tried re-installing the Open in Browser package ? Do you run atom from the command line ? When you try to run your python file, do you call python or python3 ?

    – Patol75
    Nov 15 '18 at 4:41











  • Thanks for the reply. I have script installed but it doesn't seem to work properly so I don't use it. I just tried re-installing Open in Browser, but the the issue persists. I don't run atom from the command line; I just open it like a normal program and load in project folders. I reinstalled python on my home comp and that solved the issue, but the problem persists on my work laptop after trying all of the provided solutions.

    – Matt
    Nov 15 '18 at 22:16












  • I run my scripts with script. There are two things I do. First, in the settings of script, I specify that the folder from which the script command needs to be called is the one of the current file. And second, I specify in the launching options (Ctrl + Shift + Alt + O) that the command to execute is python3. This works for me. Another question which may help: what command do you call in the terminal to use python? Because if it is python3 and that atom expects python, then that is maybe the problem.

    – Patol75
    Nov 15 '18 at 23:59














0












0








0








I had been able to run python files via Atom's Open in Browser, but now that I have uninstalled python 2.7 (still have the latest version installed) it throws an error saying I have no program associated with that file type. Any help would be appreciated!










share|improve this question














I had been able to run python files via Atom's Open in Browser, but now that I have uninstalled python 2.7 (still have the latest version installed) it throws an error saying I have no program associated with that file type. Any help would be appreciated!







python atom-editor






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 4:29









MattMatt

73




73












  • A few questions which may help. Are you using the script package ? Have you tried re-installing the Open in Browser package ? Do you run atom from the command line ? When you try to run your python file, do you call python or python3 ?

    – Patol75
    Nov 15 '18 at 4:41











  • Thanks for the reply. I have script installed but it doesn't seem to work properly so I don't use it. I just tried re-installing Open in Browser, but the the issue persists. I don't run atom from the command line; I just open it like a normal program and load in project folders. I reinstalled python on my home comp and that solved the issue, but the problem persists on my work laptop after trying all of the provided solutions.

    – Matt
    Nov 15 '18 at 22:16












  • I run my scripts with script. There are two things I do. First, in the settings of script, I specify that the folder from which the script command needs to be called is the one of the current file. And second, I specify in the launching options (Ctrl + Shift + Alt + O) that the command to execute is python3. This works for me. Another question which may help: what command do you call in the terminal to use python? Because if it is python3 and that atom expects python, then that is maybe the problem.

    – Patol75
    Nov 15 '18 at 23:59


















  • A few questions which may help. Are you using the script package ? Have you tried re-installing the Open in Browser package ? Do you run atom from the command line ? When you try to run your python file, do you call python or python3 ?

    – Patol75
    Nov 15 '18 at 4:41











  • Thanks for the reply. I have script installed but it doesn't seem to work properly so I don't use it. I just tried re-installing Open in Browser, but the the issue persists. I don't run atom from the command line; I just open it like a normal program and load in project folders. I reinstalled python on my home comp and that solved the issue, but the problem persists on my work laptop after trying all of the provided solutions.

    – Matt
    Nov 15 '18 at 22:16












  • I run my scripts with script. There are two things I do. First, in the settings of script, I specify that the folder from which the script command needs to be called is the one of the current file. And second, I specify in the launching options (Ctrl + Shift + Alt + O) that the command to execute is python3. This works for me. Another question which may help: what command do you call in the terminal to use python? Because if it is python3 and that atom expects python, then that is maybe the problem.

    – Patol75
    Nov 15 '18 at 23:59

















A few questions which may help. Are you using the script package ? Have you tried re-installing the Open in Browser package ? Do you run atom from the command line ? When you try to run your python file, do you call python or python3 ?

– Patol75
Nov 15 '18 at 4:41





A few questions which may help. Are you using the script package ? Have you tried re-installing the Open in Browser package ? Do you run atom from the command line ? When you try to run your python file, do you call python or python3 ?

– Patol75
Nov 15 '18 at 4:41













Thanks for the reply. I have script installed but it doesn't seem to work properly so I don't use it. I just tried re-installing Open in Browser, but the the issue persists. I don't run atom from the command line; I just open it like a normal program and load in project folders. I reinstalled python on my home comp and that solved the issue, but the problem persists on my work laptop after trying all of the provided solutions.

– Matt
Nov 15 '18 at 22:16






Thanks for the reply. I have script installed but it doesn't seem to work properly so I don't use it. I just tried re-installing Open in Browser, but the the issue persists. I don't run atom from the command line; I just open it like a normal program and load in project folders. I reinstalled python on my home comp and that solved the issue, but the problem persists on my work laptop after trying all of the provided solutions.

– Matt
Nov 15 '18 at 22:16














I run my scripts with script. There are two things I do. First, in the settings of script, I specify that the folder from which the script command needs to be called is the one of the current file. And second, I specify in the launching options (Ctrl + Shift + Alt + O) that the command to execute is python3. This works for me. Another question which may help: what command do you call in the terminal to use python? Because if it is python3 and that atom expects python, then that is maybe the problem.

– Patol75
Nov 15 '18 at 23:59






I run my scripts with script. There are two things I do. First, in the settings of script, I specify that the folder from which the script command needs to be called is the one of the current file. And second, I specify in the launching options (Ctrl + Shift + Alt + O) that the command to execute is python3. This works for me. Another question which may help: what command do you call in the terminal to use python? Because if it is python3 and that atom expects python, then that is maybe the problem.

– Patol75
Nov 15 '18 at 23:59













1 Answer
1






active

oldest

votes


















2














Update your system's path variables because python path is pointing to the previous version which you have uninstalled.






share|improve this answer























  • It looks like it is already set to Python36-32. I uninstalled 2.7

    – Matt
    Nov 15 '18 at 4:39











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53312449%2fcant-run-py-files-from-atom-after-uninstalling-old-python%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














Update your system's path variables because python path is pointing to the previous version which you have uninstalled.






share|improve this answer























  • It looks like it is already set to Python36-32. I uninstalled 2.7

    – Matt
    Nov 15 '18 at 4:39















2














Update your system's path variables because python path is pointing to the previous version which you have uninstalled.






share|improve this answer























  • It looks like it is already set to Python36-32. I uninstalled 2.7

    – Matt
    Nov 15 '18 at 4:39













2












2








2







Update your system's path variables because python path is pointing to the previous version which you have uninstalled.






share|improve this answer













Update your system's path variables because python path is pointing to the previous version which you have uninstalled.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 15 '18 at 4:33









Haris AnwarHaris Anwar

19116




19116












  • It looks like it is already set to Python36-32. I uninstalled 2.7

    – Matt
    Nov 15 '18 at 4:39

















  • It looks like it is already set to Python36-32. I uninstalled 2.7

    – Matt
    Nov 15 '18 at 4:39
















It looks like it is already set to Python36-32. I uninstalled 2.7

– Matt
Nov 15 '18 at 4:39





It looks like it is already set to Python36-32. I uninstalled 2.7

– Matt
Nov 15 '18 at 4:39



















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53312449%2fcant-run-py-files-from-atom-after-uninstalling-old-python%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Kleinkühnau

Makov (Slowakei)

Deutsches Schauspielhaus