### Motivation

Adopt the same versioning rule with the Node.js client, see
apache/pulsar-client-node#287.

Add an extra step to commit the version update directly before pushing
the tag. For example, fda5086

Addresses Issue #31 - we should access a string representation of the given object rather than assuming that the object itself can be concatenated with a string.

#95)

* Describe how to install the candidated wheels

* Fix the KEYS URL

…terrupted (#99)

### Motivation

Currently, when a blocking API is interrupted by a signal, `SystemError`
will be thrown. However, in this case, `PyErr_SetInterrupt` will be
called and next time a blocking API is called, `std::system_error` will
be somehow thrown.

The failure of
https://lists.apache.org/thread/cmzykd9qz9x1d0s35nc5912o3slwpxpv is
caused by this issue. The `SystemError` is not called, then
`client.close()` will be skipped, which leads to the `bad_weak_ptr`
error.

P.S. Currently we have to call `client.close()` on a `Client` instance,
otherwise, the `bad_weak_ptr` will be thrown.

However, even if we caught the `SystemError` like:

```python
    try:
        msg = consumer.receive()
        # ...
    except SystemError:
        break
```

we would still see the following error:

```
terminate called after throwing an instance of 'std::system_error'
  what():  Operation not permitted
Aborted
```

### Modifications

- Wrap `ResultInterrupted` into the `pulsar.Interrupted` exception.
- Refactor the `waitForAsyncValue` and `waitForAsyncResult` functions
  and raise `pulsar.Interrupted` when `PyErr_CheckSignals` detects a
  signal.
- Add `InterruptedTest` to cover this case.
- Remove `future.h` since we now use `std::future` instead of the
  manually implemented `Future`.
- Fix the `examples/consumer.py` to support stopping by Ctrl+C.

The new BK client is now working with newer version of Grpc, so we can upgrade and use Grpc >1.37 which comes with pre-packaged binaries.

* Bump the C++ client to 3.2.0

Fixes #116

apache/pulsar-client-cpp#266 is included in the
C++ client 3.2.0 so that #116 will be fixed.

* Change the download URL since archive.apache.org is not available now

* Revert "Change the download URL since archive.apache.org is not available now"

This reverts commit 6b92e98.

### Modifications

Add tests to verify the changes of
apache/pulsar-client-cpp#249 work for the Python
client.

Add docs to describe valid JSON fields used to create an
`AuthenticationOauth2` instance.

Fixes #114

### Motivation

Currently the `acknowledge` and `acknowledge_cumulative` methods are all
asynchronous. Even if any error happened, no exception would be raised.
For example, when acknowledging cumulatively on a consumer whose
consumer type is Shared or KeyShared, no error happens.

### Modifications

- Change these methods to synchronous and raise exceptions if the
  acknowledgment failed.
- Add `PulsarTest.test_acknowledge_failed` to test these failed cases.
- Improve the documents to describe which exceptions could be raised in
  which cases.

Fix #122 

When call an async method on Pulsar C++ client, we need to be releasing the GIL to avoid a deadlock between that and the producer lock.

Fixes #108

### Motivation

Currently the Python client uses the reader schema, which is the schema
of the consumer, to decode Avro messages. However, when the writer
schema is different from the reader schema, the decode will fail.

### Modifications

Add `attach_client` method to `Schema` and call it when creating
consumers and readers. This method stores a reference to a
`_pulsar.Client` instance, which leverages the C++ APIs added in
apache/pulsar-client-cpp#257 to fetch schema
info. The `AvroSchema` class fetches and caches the writer schema if it
is not cached, then use both the writer schema and reader schema to
decode messages.

Add `test_schema_evolve` to test consumers or readers can decode
any message whose writer schema is different with the reader schema.

### Motivation

#85 (comment)

Some targets in the API docs are referenced from the `_pulsar` module,
while the `pydoctor` command does not generate API docs for it. It's not
friendly to users, e.g. they cannot find which values could
`_pulsar.ConsumerType` be.

```
pulsar/__init__.py:695: Cannot find link target for "_pulsar.ConsumerType"
```

### Modifications

Fix the documents to describe how to include the API docs for the
`_pulsar` module when generating API docs. It also fixes some other
warnings when running the `pydoctor` command.