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 pablogsal
Recipients Elvis.Pranskevichus, Mark.Shannon, gregory.p.smith, larry, miss-islington, pablogsal, vstinner, yselivanov
Date 2022-01-12.02:03:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641953014.31.0.139218114335.issue46347@roundup.psfhosted.org>
In-reply-to
Content
> Could it wait for 3.10.2 already scheduled for four weeks from now?

I don't feel comfortable leaving a ton of Cython functions leaking memory constantly on many function calls. According to https://github.com/MagicStack/asyncpg/issues/874 asyncpg can leak quite a lot of memory depending on your usage pattern.

Even if this is the first time we heard about this problem, I think this is important enough to justify a extra release.
History
Date User Action Args
2022-01-12 02:03:34pablogsalsetrecipients: + pablogsal, gregory.p.smith, vstinner, larry, Elvis.Pranskevichus, Mark.Shannon, yselivanov, miss-islington
2022-01-12 02:03:34pablogsalsetmessageid: <1641953014.31.0.139218114335.issue46347@roundup.psfhosted.org>
2022-01-12 02:03:34pablogsallinkissue46347 messages
2022-01-12 02:03:34pablogsalcreate