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 dgelessus
Recipients anthonypjshaw, dgelessus, eryksun, freakboy3742
Date 2019-05-13.10:17:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557742641.11.0.102252426783.issue36880@roundup.psfhosted.org>
In-reply-to
Content
Thank you for looking into this! I can confirm that Eryk Sun's change fixes the issue for me locally.

I'm up for making the patch for this. Regarding tests, I see there are already some refcount-related ctypes tests in Lib/ctypes/test/test_refcounts.py - should I add another test case there that reproduces this situation and ensures that None's refcount is unaffected? (I imagine testing against None's refcount will be a bit fragile, so it might be best to call the previously-buggy function in a loop and check afterwards that None's refcount hasn't changed significantly.)
History
Date User Action Args
2019-05-13 10:17:21dgelessussetrecipients: + dgelessus, freakboy3742, eryksun, anthonypjshaw
2019-05-13 10:17:21dgelessussetmessageid: <1557742641.11.0.102252426783.issue36880@roundup.psfhosted.org>
2019-05-13 10:17:21dgelessuslinkissue36880 messages
2019-05-13 10:17:20dgelessuscreate