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 pitrou
Recipients eric.araujo, neologix, pitrou, poq, r.david.murray, telmich
Date 2012-03-26.13:43:38
SpamBayes Score 5.57853e-05
Marked as misclassified No
Message-id <1332769419.59.0.175284924112.issue14228@psf.upfronthosting.co.za>
In-reply-to
Content
> Why an environment variable instead of a command line switch (as
> suggested by Ian Jackson)? Shouldn't a script be able to decide for
> itself how it handles signals?

Because the available space for command line switches is rather limited, and this isn't an important option.

This issue applies only to POSIX systems AFAIK, and it's easy to force an env var when running an executable ("MYENVVAR=foo python ...").
History
Date User Action Args
2012-03-26 13:43:39pitrousetrecipients: + pitrou, eric.araujo, r.david.murray, neologix, poq, telmich
2012-03-26 13:43:39pitrousetmessageid: <1332769419.59.0.175284924112.issue14228@psf.upfronthosting.co.za>
2012-03-26 13:43:39pitroulinkissue14228 messages
2012-03-26 13:43:38pitroucreate