ChatExchange icon indicating copy to clipboard operation
ChatExchange copied to clipboard

A Python API for talking to Stack Exchange chat

Results 19 ChatExchange issues
Sort by recently updated
recently updated
newest added

When receiving messages from SE, it raised a 500 error. After this, it no longer read any more messages. This is probably due to the exception killing off the reader...

We currently cache messages in `client` https://github.com/Manishearth/ChatExchange/blob/master/chatexchange/client.py#L71 However, these are not updated on edits, and it's cached indefinitely. We should have: - [ ] A way to keep these up...

Some tests are failing because pins expire. We might want to make the assertion optional ("expected failure"). I'll look into whether or not pytest supports this.

As discussed in #59, we want to have some universal throttling mechanism for client requests. --- ### Throttling When we post a new message, or edit one, the requests are...

enhancement

As discussed in #59, the public Client interface should be entirely thread-safe, whatever the users do. (The current implementation has probably unsafe behaviour internally, without any help from the users.)...

enhancement

When message.content is done, it leaves in the entity names. I'm not sure if that's a bug, but I was expecting them to be replaced by their character equivalent.

Say I send a message I would like to modify later. Do I have to look at the events to find that message ID (...or way better: the message object),...

Perhaps some common room methods like `send_message` and `watch` should be reexported on `Client` with an extra room id parameter for convenience?

question

Not a priority at all, but since it was mentioned, I thought I'd create a ticket to discuss it. I don't think there's any official way to login to programmatically...

enhancement