René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Deprecate the unused `tokenize._compile` function","articleBody":"# Feature or enhancement\n\n### Proposal:\n\n~~Remove the unused `tokenize._compile` function.~~ EDIT: Deprecate the unused `tokenize._compile` function.\n\nIt very much looks like the internal `tokenize._compile` function hasn't been needed since GH-104323 when it was initially removed, but it was mechanically brought back to `tokenize` in GH-104722 to fix GH-104719.\n\nFrom a quick search, it seems that, prior to GH-104323, `tokenize._compile` was only used internally in `tokenize._tokenize`.\n\nMost of the fairly fresh [code I skimmed through on GitHub](https://github.com/search?q=tokenize._compile\u0026type=code) operating on `tokenize._compile` properly checks if Python is version \u003c3.10 / `tokenize._compile` exists.\n\nExcept [`CheetahTemplate3`](https://github.com/CheetahTemplate3/cheetah3/blob/071b8a0faf5eb7728d771b5dd47d0806316f4bee/Cheetah/Parser.py#L24), so removing `tokenize._compile` immediately could break them -- we need to deprecate first.\n\nIn terms of benefits of removing this at some point: it wouldn't necessarily improve the import time of `tokenize` as long as `re` still imports `functools` to cache template compilation. Therefore, removing `tokenize._compile` in the future is just a small cleanup that yields no other benefits than smaller, less bloated code.\n\n### Has this already been discussed elsewhere?\n\nThis is a minor feature, which does not need previous discussion elsewhere\n\n### Links to previous discussion of this feature:\n\n_No response_","author":{"url":"https://github.com/johnslavik","@type":"Person","name":"johnslavik"},"datePublished":"2025-12-20T05:01:19.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/143009/cpython/issues/143009"}