TwitterStream not raising TwitterHTTPError

[jcollins-va]

This may not be a bug, but perhaps a misunderstanding of how Twitter works with this library.

For a single OAuth access token, if I create one filter stream and then a second one, Twitter stops sending for the first stream. Twitter docs (https://dev.twitter.com/docs/streaming-apis/streams/public) say:

Each account may create only one standing connection to the public endpoints, 
and connecting to a public stream more than once with the same account credentials 
will cause the oldest connection to be disconnected.

However, I am never seeing the TwitterHTTPError raised on my first TwitterStream iterator.

Without this raise, I'm unsure as to how I can tell if a particular stream is dead or not?

[sixohsix]

Good catch. It definitely should raise an error on close. I will have to look into this (but I'm not sure when I'll get to it.)

[RouxRC]

I think this could be closed now the stream logic was entirely redone, @jcollins-va can you confirm so?