Inconsistent documentation: are interned strings immortal or not?
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Documentation
From HOWTO about python free-threading:
As of the 3.14 release, immortalization is limited to:
- Code constants: numeric literals, string literals, and tuple literals composed of other constants.
- Strings interned by sys.intern().
From sys.intern():
Interned strings are not immortal; you must keep a reference to the return value of intern() around to benefit from it.
So, are the interned strings immortal or not?
Linked PRs
- gh-144176
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the immortalization section in the free-threading HOWTO with the sys.intern() documentation and the linked PR gh-144176. Check which statement reflects the documented behavior, then update the conflicting documentation so both sections agree and verify the rendered wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100