About this page

Issue 33231: Potential memory leak in normalizestring() - Python tracker

https://bugs.python.org/issue33231

“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. Created on 2018-04-05 12:34 by methane, last changed 2022-04-11 14:58 by admin. This issue is now closed. URL Status Linked Edit PR 6386 merged...” (from the page’s text)

In short: Learn how a potential memory leak in Python's normalizestring() function was resolved in versions 3.6, 3.7, and 3.8. Discover the optimized method used to prevent unnecessary allocation/deallocation. (AI summary)

Topic: Community Forums › Technical Forums
Quality: Quality 88 scored 12 Aug 2025
Language: english
Text on page: 3,516 characters
Page size: 20 kB
Answered: OK (200), HTML
Last read: 7 Jul 2025
In our index since: 7 Jul 2025
Safe search: Not checked yet
Links to it: No other site we've read links here yet

Tools for this page

Other sites that can tell you more. Plain links: we don't track where you go.

About the site

Domain owner ICANN registration lookup
Certificates certificate transparency, subdomains
Safety check Safe Browsing status
Trackers The Markup's Blacklight
Is it down? for everyone, or just you

Discussions

Hacker News stories linking here
Reddit posts from this site
Wikipedia articles mentioning the site

For web makers

PageSpeed Lighthouse report
HTML validator W3C
Accessibility WAVE by WebAIM
Security headers

Who links to it

We haven't seen any links to this page yet. That usually means we haven't crawled the pages that link to it, not that there are none.

“Not rated yet” and similar notes are shown on purpose: we say what we haven't measured, so the page doesn't look emptier or better than it is.