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 neologix
Recipients giampaolo.rodola, loewis, neologix, pitrou, qyb
Date 2012-04-24.20:00:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3Chu-PV9n8N-kOkXq0a+EUroBr2HAuMfEAX7U7yYKQrA@mail.gmail.com>
In-reply-to <1334151563.67.0.887827722652.issue1522400@psf.upfronthosting.co.za>
Content
Here's a cleanup up patch against default.
However, I don't have any IrDA capable device neither, so I won't be
able to help much. I'll ask on python-dev if someone can help.
As for the manual decoding, AFAICT you'll have the same issue with CAN sockets.
The real question is really "how high-level should the socket module be?".
Because if we added let's say and IRDASocket type, then we could
easily add helper functions to and methods to e.g. list available IrDA
devices, decode fields, etc.
Same thing holds for CAN sockets, and one could imagine we could also
maybe add a MulticastSocket that would make joining/leaving a
multicast group easy (because it is a pain), etc.
Files
File name Uploaded
irda-default.diff neologix, 2012-04-24.20:00:22
History
Date User Action Args
2012-04-24 20:00:23neologixsetrecipients: + neologix, loewis, pitrou, giampaolo.rodola, qyb
2012-04-24 20:00:22neologixlinkissue1522400 messages
2012-04-24 20:00:22neologixcreate