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 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 <>
In-reply-to <>
> (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.
Date User Action Args
2012-02-23 22:13:03loewissetrecipients: + loewis, brett.cannon, arigo, nascheme, glchapman, gregory.p.smith, ncoghlan, belopolsky, pitrou, christian.heimes, andrea.corbellini, flox, cburroughs, BreamoreBoy
2012-02-23 22:13:02loewislinkissue812369 messages
2012-02-23 22:13:02loewiscreate