Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6775135
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T15:52:15+00:00 2026-05-26T15:52:15+00:00

Is it a bad coding practice to call the exit() function in Python repeatedly?

  • 0

Is it a bad coding practice to call the exit() function in Python repeatedly?

I’m working on a command-line tool, so there are multiple function definitions… Basically:

def usage()
def error(arg1)
def find(arg1, arg2)

In the end of usage() I call exit(), which I assume it’s OK, but it’s also called in the success of find(), and in error() (which is called in the failure of find().

As you can see, exit() is being called many times in my code, and I wasn’t sure if this is actually a bad coding practice.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T15:52:16+00:00Added an answer on May 26, 2026 at 3:52 pm

    Not really bad practice IMO – just make sure you return an exit code reflecting the different exit points whenever that might be useful to the calling process…

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Why is it bad practice to declare variables on one line? e.g. private String
I want to understand if the following coding practice is good or bad practice.
I understand that this is bad programming practice and redundant coding but I am
Why is it bad to name a variable id in Python?
Are circular class dependencies bad from a coding style point of view? Example: In
Please forgive the extreme-beginner style of coding. I'm working with PHP and JSON strings
Is it considered bad coding to put a break in the default part of
How bad is it to use Location Manager to retrieve the location information when
What bad things happen at the moment document.write() is invoked? I've heard bits and
Either I had a bad dream recently or I am just too stupid to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.