Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Rejected.
This suggested edit was rejected about 1 year ago by r~~‭:

83 / 255
  • If `systemd-run` [works for you](https://linux.codidact.com/posts/289510#answer-289511), that is probably the simplest thing you can do here.
  • Otherwise, you can use `os.fork()` [from within Python](https://software.codidact.com/posts/289509#answer-289512) to spawn a child that stays alive after the parent exits.
  • If someone else is reading this based on the title, but is writing an industrial Python application that doesn't immediately exit, wants to schedule future tasks, and have those tasks be robust across various system events, neither of those solutions is likely to be as robust as using a dedicated service with a name like task scheduler, task queue, or message broker. [Celery](https://docs.celeryq.dev/en/stable/getting-started/introduction.html) is a good example.
  • Solutions
  • -
  • The simplest thing you can probably do here is to use [`systemd-run`](https://linux.codidact.com/posts/289510#answer-289511).
  • If that doesn't work for you, you can use `os.fork()` [from within Python](https://software.codidact.com/posts/289509#answer-289512) to spawn a child that stays alive after the parent exits.
  • Note
  • -
  • If someone else is reading this based on the title, but is writing an industrial Python application that doesn't immediately exit, wants to schedule future tasks, and have those tasks be robust across various system events, neither of those solutions is likely to be as robust as using a dedicated service with a name like task scheduler, task queue, or message broker. [Celery](https://docs.celeryq.dev/en/stable/getting-started/introduction.html) is a good example.

Suggested about 1 year ago by meta user‭