Message154094
| Author |
loewis |
| Recipients |
BreamoreBoy, andrea.corbellini, arigo, belopolsky, brett.cannon, cburroughs, christian.heimes, flox, glchapman, gregory.p.smith, loewis, nascheme, ncoghlan, pitrou |
| Date |
2012年02月23日.22:13:02 |
| SpamBayes Score |
4.522697e-08 |
| Marked as misclassified |
No |
| Message-id |
<4F46B9ED.5070909@v.loewis.de> |
| In-reply-to |
<1329499155.03.0.0606955045376.issue812369@psf.upfronthosting.co.za> |
| Content |
> (This is just a report about PyPy's situation; I understand that the
> situation in CPython is a bit more delicate if CPython is embedded in
> a larger process.)
I think that would indeed be unacceptable for Python - there is a
long-standing expectation that we free all memory that we allocated,
as well as release any other resources that we hold. There are also
expectations wrt. running atexit code. So there clearly must be a
shutdown procedure. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年02月23日 22:13:03 | loewis | set | recipients:
+ loewis, brett.cannon, arigo, nascheme, glchapman, gregory.p.smith, ncoghlan, belopolsky, pitrou, christian.heimes, andrea.corbellini, flox, cburroughs, BreamoreBoy |
| 2012年02月23日 22:13:02 | loewis | link | issue812369 messages |
| 2012年02月23日 22:13:02 | loewis | create |
|