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 gappleto97
Recipients asvetlov, gappleto97
Date 2019-06-20.14:11:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <4B449CFA-DA4E-49B2-AF3A-1057AF59EDD7@gabeappleton.me>
In-reply-to <1561028098.86.0.816855722789.issue37345@roundup.psfhosted.org>
Content
Its true that this doesnt exist at the C level, however I worry that having it purely through getsockopt() and setsockopt() would make things more confusing, so I added it as a helper function.

I can remove it in lieu of documentation if that would block merging, though I dont think that is the right move here.

On June 20, 2019 10:54:58 AM UTC, Andrew Svetlov <report@bugs.python.org> wrote:
>
>Andrew Svetlov <andrew.svetlov@gmail.com> added the comment:
>
>Adding new constants like socket.IPPROTO_UDPLITE is fine.
>The question is: why we need a new function?
>There is no set_send_checksum_coverage() on C level IIRC
>
>----------
>nosy: +asvetlov
>
>_______________________________________
>Python tracker <report@bugs.python.org>
><https://bugs.python.org/issue37345>
>_______________________________________
History
Date User Action Args
2019-06-20 14:11:23gappleto97setrecipients: + gappleto97, asvetlov
2019-06-20 14:11:23gappleto97linkissue37345 messages
2019-06-20 14:11:23gappleto97create