homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, ethan.furman, mark.dickinson, pitrou, serhiy.storchaka, skrah, terry.reedy
Date 2015年04月27日.17:23:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430155402.93.0.150452794064.issue24053@psf.upfronthosting.co.za>
In-reply-to
Content
> Then precisely, those new codes should go in the os module as well.
What is your logic? Having os.EX_ codes in os does not help as far as sys.exit() is concerned: no-one is using them and they are not available on all platforms. If we add EXIT_FAILURE and EXIT_SUCCESS to os now, we will only create confusion: should I use os.EX_OK or os.EXIT_SUCCESS?
Note that sys.exit() is different from os._exit(). It may not even result in termination of the interpreter. Why should users of sys.exit() be required to import os if they want to indicate a failure?
History
Date User Action Args
2015年04月27日 17:23:22belopolskysetrecipients: + belopolsky, terry.reedy, mark.dickinson, pitrou, skrah, ethan.furman, serhiy.storchaka
2015年04月27日 17:23:22belopolskysetmessageid: <1430155402.93.0.150452794064.issue24053@psf.upfronthosting.co.za>
2015年04月27日 17:23:22belopolskylinkissue24053 messages
2015年04月27日 17:23:22belopolskycreate

AltStyle によって変換されたページ (->オリジナル) /