Skip to main content

Starting a python script from another before it crashes

I'm trying to make some project code I have written, more resilient to crashes, except the circumstances of my previous crashes have all been different. So that I do not have to try and account for every single one, I thought I'd try to get my code to either restart, or execute a copy of itself in place of it and then close itself down gracefully, meaning its replacement, because it's coded identically, would in essence be the same as restarting from the beginning again. The desired result for me would be that while the error resulting circumstances are present, my code would be in a program swap out, or restart loop until such time as it can execute its code normally again....until the next time it faces a similar situation.

To experiment with, I've written two programs. I'm hoping from these examples someone will understand what I am trying to achieve. I want the first script to execute, then start the execute process for the second (in a new terminal) before closing itself down gracefully.

Is this even possible?

Thanks in advance.

first.py

#!/usr/bin/env python
#!/bin/bash
#first.py

import time
import os
import sys
from subprocess import run
import subprocess

thisfile = "first"
#thisfile = "second"

time.sleep(3)
while thisfile == "second":
    print("this is the second file")
    time.sleep(1)
    #os.system("first.py")
    #exec(open("first.py").read())
    #run("python "+"first.py", check=False)
    #import first
    #os.system('python first.py')
    #subprocess.call(" python first.py 1", shell=True)
    os.execv("first.py", sys.argv)
    print("I'm leaving second now")
    break
while thisfile == "first":
    print("this is the first file")
    time.sleep(1)
    #os.system("second.py")
    #exec(open("second.py").read())
    #run("python "+"second.py", check=False)
    #import second
    #os.system('python second.py')
    #subprocess.call(" python second.py 1", shell=True)
    os.execv("second.py", sys.argv)
    print("I'm leaving first now")
    break
time.sleep(1)
sys.exit("Quitting")

second.py (basically a copy of first.py)

#!/usr/bin/env python
#!/bin/bash
#second.py

import time
import os
import sys
from subprocess import run
import subprocess

#thisfile = "first"
thisfile = "second"

time.sleep(3)
while thisfile == "second":
    print("this is the second file")
    time.sleep(1)
    #os.system("first.py")
    #exec(open("first.py").read())
    #run("python "+"first.py", check=False)
    #import first
    #os.system('python first.py')
    #subprocess.call(" python first.py 1", shell=True)
    os.execv("first.py", sys.argv)
    print("I'm leaving second now")
    break
while thisfile == "first":
    print("this is the first file")
    time.sleep(1)
    #os.system("second.py")
    #exec(open("second.py").read())
    #run("python "+"second.py", check=False)
    #import second
    #os.system('python second.py')
    #subprocess.call(" python second.py 1", shell=True)
    os.execv("second.py", sys.argv)
    print("I'm leaving first now")
    break
time.sleep(1)
sys.exit("Quitting")

I have tried quite a few solutions as can be seen with my hashed out lines of code. Nothing so far though has given me the result I am after unfortunately.



source https://stackoverflow.com/questions/74593058/starting-a-python-script-from-another-before-it-crashes

Comments

Popular posts from this blog

Confusion between commands.Bot and discord.Client | Which one should I use?

Whenever you look at YouTube tutorials or code from this website there is a real variation. Some developers use client = discord.Client(intents=intents) while the others use bot = commands.Bot(command_prefix="something", intents=intents) . Now I know slightly about the difference but I get errors from different places from my code when I use either of them and its confusing. Especially since there has a few changes over the years in discord.py it is hard to find the real difference. I tried sticking to discord.Client then I found that there are more features in commands.Bot . Then I found errors when using commands.Bot . An example of this is: When I try to use commands.Bot client = commands.Bot(command_prefix=">",intents=intents) async def load(): for filename in os.listdir("./Cogs"): if filename.endswith(".py"): client.load_extension(f"Cogs.{filename[:-3]}") The above doesnt giveany response from my Cogs ...

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Where and how is this Laravel kernel constructor called? [closed]

Where and how is this Laravel kernel constructor called? public fucntion __construct(Application $app, $Router $roouter) { } I have read the documentation and some online tutorial but I can find any clear explanation. I am learning Laravel and I am wondering where does this kernel constructor receives its arguments from. "POSTMOTERM" CLARIFICATION: Here is more clarity.I have checked the boostrap/app.php and it is only used for boostrapping the interfaces into the container class. What is not clear to me is where and how the Kernel class is instatiated and the arguments passed to the object calling the constructor.Something similar to; obj = new kernel(arg1,arg2) or, is the framework using some magic functions somewhere? Special gratitude to those who burn their eyeballs and brain cells on this trivia before it goes into a full blown menopause alias "MARKED AS DUPLICATE". To some of the itchy-finger keyboard warriors, a.k.a The mods,because I believe in th...