Repository navigation
SocketCAN fails on Python versions 3.3 & 3.4 and on PyPy 3 #274
Description
This can be found in the Python 3.5 change log and the official docs:
The socket module now exports the CAN_RAW_FD_FRAMES constant on linux 3.6 and greater.
If you look at this CI test, socketcan-native fails for Python versions 3.3 & 3.4 because it uses CAN_RAW_FD_FRAMES on these platforms. How can a interface register itself as not being able to handle CAN FD frames?
There is also another Problem on PyPy 3: module 'socket' has no attribute 'CAN_RAW'.
Activity
[-]The socket module now exports the CAN_RAW_FD_FRAMES constant on linux 3.6 and greater.[/-][+]SocketCAN fails on Python versions 3.3 & 3.4 because it uses CAN_RAW_FD_FRAMES[/+]felixdivo commentedon Mar 2, 2018
Do we even want to support these Python versions any more? At least Python 3.3 has reached its end of life.
felixdivo commentedon Mar 2, 2018
See the bottom of
test/back2back_test.pyon branchmore-tests(or maybedeveloponce it is merged).[-]SocketCAN fails on Python versions 3.3 & 3.4 because it uses CAN_RAW_FD_FRAMES[/-][+]SocketCAN fails on Python versions 3.3 & 3.4 and on PyPy[/+][-]SocketCAN fails on Python versions 3.3 & 3.4 and on PyPy[/-][+]SocketCAN fails on Python versions 3.3 & 3.4 and on PyPy 3[/+]felixdivo commentedon Apr 4, 2018
I propose this change:
socketcan_ctypeson Python 3.4 to be able to use CAN FD framessocketcan_ctypeson all PyPy versions, sincesocket.CAN_RAW_*seems to be unavailable there (where are the docs for that?)