Author Tim.Tisdall
Recipients Tim.Tisdall, docs@python, martin.panter
Date 2015-09-10.13:02:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441890157.31.0.806017964161.issue25043@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure how to unit test a constant...  it's just a string.  If you're asking for a unit test for when you'd actually make use of the constant, I haven't been able to figure out that situation yet.  It seems like in Bluez 4.101 it's used to issue a command to all interfaces (but in contexts I don't quite understand), but in Bluez 5.XX there's no example or documentation of its use (it remains as a constant, though).  [looking through the Bluez git, I found where the constant was added in 2004 and the log message is simply "Add BDADDR_ALL constant"; http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=c7b26f3e5d03e1d54dfb945e5ca0c041da524348 ]
History
Date User Action Args
2015-09-10 13:02:37Tim.Tisdallsetrecipients: + Tim.Tisdall, docs@python, martin.panter
2015-09-10 13:02:37Tim.Tisdallsetmessageid: <1441890157.31.0.806017964161.issue25043@psf.upfronthosting.co.za>
2015-09-10 13:02:37Tim.Tisdalllinkissue25043 messages
2015-09-10 13:02:37Tim.Tisdallcreate