Skip to content

gh-145685: Remove _PySeqLock that is not used anymore (gh-155243) - #155243

Merged
colesbury merged 1 commit into
python:mainfrom
maurycy:remove-pyseq-lock
Aug 6, 2026
Merged

gh-145685: Remove _PySeqLock that is not used anymore (gh-155243)#155243
colesbury merged 1 commit into
python:mainfrom
maurycy:remove-pyseq-lock

Conversation

@maurycy

@maurycymaurycy commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

As per #145685 (comment):

maurycy@gimel cpython (main 9ccd5bb) % rg _PySeqLock
Objects/typeobject.c
11:#include "pycore_lock.h" // _PySeqLock_*
Include/internal/pycore_lock.h
221:} _PySeqLock;
224:PyAPI_FUNC(void) _PySeqLock_LockWrite(_PySeqLock *seqlock);
227:PyAPI_FUNC(void) _PySeqLock_UnlockWrite(_PySeqLock *seqlock);
231:PyAPI_FUNC(void) _PySeqLock_AbandonWrite(_PySeqLock *seqlock);
234:PyAPI_FUNC(uint32_t) _PySeqLock_BeginRead(_PySeqLock *seqlock);
238:PyAPI_FUNC(int) _PySeqLock_EndRead(_PySeqLock *seqlock, uint32_t previous);
242:PyAPI_FUNC(int) _PySeqLock_AfterFork(_PySeqLock *seqlock);
Python/lock.c
579:void _PySeqLock_LockWrite(_PySeqLock *seqlock)
600:void _PySeqLock_AbandonWrite(_PySeqLock *seqlock)
607:void _PySeqLock_UnlockWrite(_PySeqLock *seqlock)
614:uint32_t _PySeqLock_BeginRead(_PySeqLock *seqlock)
625:int _PySeqLock_EndRead(_PySeqLock *seqlock, uint32_t previous)
640:int _PySeqLock_AfterFork(_PySeqLock *seqlock)

Hardly newsworthy?

@maurycymaurycy changed the title gh-145685: _PySeqLock not used anymoregh-145685: Remove _PySeqLock that is not used anymoreAug 5, 2026
@colesburycolesbury changed the title gh-145685: Remove _PySeqLock that is not used anymoregh-145685: Remove _PySeqLock that is not used anymore (gh-155243)Aug 6, 2026
@colesbury
colesbury merged commit d2f4649 into python:mainAug 6, 2026
54 checks passed
@maurycy
maurycy deleted the remove-pyseq-lock branch August 6, 2026 08:16
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@maurycy@colesbury