- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message240912
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 | jpe |
|---|---|
| Recipients | BreamoreBoy, asvetlov, jpe, pitrou, r.david.murray, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2015-04-14.15:33:37 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1429025617.62.0.14062107332.issue14484@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I've created issue #23948 for the idea of deprecating os.kill(). Is a patch needed for adding a return in the error case? It's that way in 2.7 and I'm struggling to come up with a reason why it shouldn't be added other than strict backward compatibility. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-04-14 15:33:37 | jpe | set | recipients: + jpe, pitrou, vstinner, tim.golden, r.david.murray, asvetlov, BreamoreBoy, zach.ware, steve.dower |
| 2015-04-14 15:33:37 | jpe | set | messageid: <1429025617.62.0.14062107332.issue14484@psf.upfronthosting.co.za> |
| 2015-04-14 15:33:37 | jpe | link | issue14484 messages |
| 2015-04-14 15:33:37 | jpe | create | |

