Tim Abbott

@PIG208 FYI as well; this is probably one of the more important features for us to add to the Python API bindings. @neiljp also FYI, since this may have some...

The goal as stated here is just to have things written with the python-zulip-api transparently handle how to call endpoints (E.g. if we rename an endpoint or we change how...

@PIG208 I think this is probably the most important issue for the Python bindings. I think in particular we want to pass all the `client_capabilities` [currently documented](https://chat.zulip.org/api/register-queue#parameter-client_capabilities) by default, to...

Thanks for the report! I agree. @eeshangarg do you have time to try moving this?

@arnavkohli can you clean up the commit history here? Check out our [GitHub guide](https://zulip.readthedocs.io/en/latest/git-guide.html) and [commit guidelines](https://zulip.readthedocs.io/en/latest/contributing/version-control.html) for more details.

The problem is that your firewall is blocking outgoing HTTP access to Zulip's dependencies. That code only runs when building an image, so your actual problem may have been not...

I merged the first bit of this, after some changes to variable names etc. Want to spend some more time thinking about the rest.

@Ponni-M can you restructure the commits to first refactor the `/api/` prefix stuff, with a commit message explaining why that's correct, and then one adding the new endpoint? Check out...

Yes, though we don't recommend it from a security perspective.

Yes, it's easy to do and easy to return. If you're running this Docker image off of master in both this repo and the zulip/zulip one, you can just set...