Update documentation: p4python 2025.2 fixes GIL blocking in connect()#1
Merged
Conversation
…ocking connect() Co-authored-by: kristjanvalur <6009543+kristjanvalur@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update README to reflect perforce p4python bug fix
Update documentation: p4python 2025.2 fixes GIL blocking in connect()
Jan 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The GIL blocking issue in
connect()/aconnect()was fixed in p4python 2025.2 per release notes. The prominent warning is no longer warranted.Changes
The note still informs users about the historical issue but doesn't dominate the documentation. No code changes required—no comments referenced this caveat.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.