Fix timeout value on reader thread wait in SMS send example

[devegied]

timeout value of 2**31 in join was returning immediately on Raspberry Pi

[coveralls]

Coverage remained the same at 89.804% when pulling c7a476b on devegied:master into 5c816ba on babca:master.

[coveralls]

Coverage increased (+0.01%) to 89.814% when pulling fe890ca on devegied:master into 5c816ba on babca:master.

[mmmcorpsvit]

in MS windows too return on default value
where depend from OS this value ? this constant?

[lcnittl]

Thank you for your PR

If you can get rid of the 2 commits that duplicate #76 this can be merged

[lcnittl]

I believe that a newer release of threading treats numbers bigger than 2**29 (have not tested everything between, but 2**30 does this already) like a 0 timeout. Maybe some number conversion somewhere deeper that results in a negative number?
In any case this should be safe to be removed, as the deafult timeout=None waits indefinitely.