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 ronaldoussoren
Recipients Mark.Shannon, gvanrossum, petr.viktorin, ronaldoussoren, vstinner
Date 2021-02-12.10:12:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1613124746.26.0.194358480037.issue43054@roundup.psfhosted.org>
In-reply-to
Content
To channel Victor: Another thing to look into is to introduce accessors for struct fields in category 1 and 2 so that the struct can be made private in the future.

The difference between category 1 and 2 is sadly not very clear cut. Anything defined in public headers could be used 3th-party code.

In this particular instance there is no documentation for the fields of the struct, which may indicate that the struct is private. However, this struct is used by code outside of the stdlib and there are currently no accessors that can replace this usage.
History
Date User Action Args
2021-02-12 10:12:26ronaldoussorensetrecipients: + ronaldoussoren, gvanrossum, vstinner, petr.viktorin, Mark.Shannon
2021-02-12 10:12:26ronaldoussorensetmessageid: <1613124746.26.0.194358480037.issue43054@roundup.psfhosted.org>
2021-02-12 10:12:26ronaldoussorenlinkissue43054 messages
2021-02-12 10:12:26ronaldoussorencreate