[issue37085] Expose additional socket constants for CAN_BCM flags

Tal Einat added the comment: Karl, many thanks for bringing this up, making a PR and iterating on it with me! -- nosy: +taleinat resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 ___ Python tracker

[issue37085] Expose additional socket constants for CAN_BCM flags

miss-islington added the comment: New changeset d8b914a30b0849476345a19ce0a0ab1ade171b19 by Miss Islington (bot) in branch '3.8': bpo-37085: Expose SocketCAN bcm_msg_head flags (GH-13646) https://github.com/python/cpython/commit/d8b914a30b0849476345a19ce0a0ab1ade171b19 -- nosy:

[issue37085] Expose additional socket constants for CAN_BCM flags

Change by miss-islington : -- pull_requests: +14800 pull_request: https://github.com/python/cpython/pull/15049 ___ Python tracker ___

[issue37085] Expose additional socket constants for CAN_BCM flags

Łukasz Langa added the comment: New changeset 31c4fd2a10d90beaa37d630e5f74a471e14e089d by Łukasz Langa (karl ding) in branch 'master': bpo-37085: Expose SocketCAN bcm_msg_head flags (#13646) https://github.com/python/cpython/commit/31c4fd2a10d90beaa37d630e5f74a471e14e089d -- nosy:

[issue37085] Expose additional socket constants for CAN_BCM flags

Change by Karl Ding : -- keywords: +patch pull_requests: +13541 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13646 ___ Python tracker ___

[issue37085] Expose additional socket constants for CAN_BCM flags

New submission from Karl Ding : When reading through the values exposed via the socket library, I noticed that currently, only the SocketCAN BCM opcode enums are exposed via the socket constants. These correspond to the following from the Linux headers: enum {