0

I've encountered this problem a couple of days ago, which is around time when I updated python and some packages.

  1. scripts run perfectly fine when I'm using Spyder,

  2. scripts run perfectly fine when I'm using Anaconda command prompt and type:

    python 'filepath\filename.py'

  3. scripts stop just after the start if I use scheduler (I use TaskTillDawn) or I run a windows shortcut 

    python "filepath\filename.py"

    that then automatically converts to:

    c:\ProgramData\Anaconda3\python.exe "filepath\filename.py"

All of the scripts were running fine before, through shortcuts, schedules etc.

Maybe the solution is obvious, but I don't see it, so any help would be appreciated. If you need more info, just tell me what it is :)

Cheers,

Improve this question
2
  • 1
    May be its helpful to do vise-versa, stackoverflow.com/questions/46437863/… Commented Nov 8, 2019 at 12:26
  • 1
    It may not be enough to simply point to the Anaconda-distribution's Python interpreter since some packages edit the environment variables during env activatiion. Instead, you could try C:\ProgramData\Anaconda3\Scripts\conda.exe run -n base python 'filepath\filename.py'. You may need to adjust the path to conda.exe since I may not be recalling correctly where it is on Windows. I'm also assuming you are talking about your base env. Commented Nov 8, 2019 at 15:48
Related questions
4
Cannot run Python script twice without restarting Spyder
2
opening Python scripts with spyder
0
Spyder IDE: Need to press 'run script' twice to successfully execute Python script
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.