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.

Author serhiy.storchaka
Recipients berker.peksag, davin, larry, pitrou, rbcollins, rhettinger, serhiy.storchaka, terry.reedy, vstinner
Date 2021-09-27.11:28:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632742098.19.0.401206549606.issue24391@roundup.psfhosted.org>
In-reply-to
Content
In the last version of PR 20534, the reprs will be similar to proposed by Larry in msg244958, except that a colon is used to separate an address from status, and keyword names are used for values.

<threading.Semaphore at 0xb710ec8c: value=10>
<threading.BoundedSemaphore at 0xb6ff1d6c: value=7/10>
<threading.Event at 0xb710ec8c: unset>
<threading.Event at 0xb710ec8c: set>
<threading.Barrier at 0xb6ff1d6c: waiters=0/10>
<threading.Barrier at 0xb6ff1d6c: waiters=3/10>
<threading.Barrier at 0xb6ff1d6c: broken>

It is closer to existing reprs, I'm going to rewrite reprs of locks, conditions and synchronization primitives in asyncio and multiprocessing to match this style: move status after type and address, remove parenthesis, brackets and commas, use "=" instead of ":" for named values, use "/" with maximal values, etc.
History
Date User Action Args
2021-09-27 11:28:18serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, terry.reedy, pitrou, vstinner, larry, rbcollins, berker.peksag, davin
2021-09-27 11:28:18serhiy.storchakasetmessageid: <1632742098.19.0.401206549606.issue24391@roundup.psfhosted.org>
2021-09-27 11:28:18serhiy.storchakalinkissue24391 messages
2021-09-27 11:28:18serhiy.storchakacreate