ISSUE 2377 : Relax grpcio requirement for python client to support python3.8 on mac os

[ca-simone-chiorazzo]

Descriptions of the changes in this PR:

Require a grpcio version that is minor of 1.28. This allow to install the 1.27.2 that has a pre-compiled wheel for python 3.8 on mac os.
Add tests for python 3.8

Motivation

grpcio 1.25.0 does not allow the installation using python 3.8 on mac os x. This is due to the fact that the pre-compiled wheels have not been published before 1.26.0

Changes

Updated the setup.py to relax a bit the requirement for grpcio
Add python3.8 as tested version
Updated the setup.py to install the latest pymmh3 version. Note: master tests are broken, I've updated the library and removed the 'signed' parameter that does not exists not anymore.

Master Issue: #

cc @eolivelli

---

In order to uphold a high standard for quality for code contributions, Apache BookKeeper runs various precommit
checks for pull requests. A pull request can only be merged when it passes precommit checks.

---

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

If this PR is a BookKeeper Proposal (BP):

• Make sure the PR title is formatted like:
  <BP-#>: Description of bookkeeper proposal
e.g. BP-1: 64 bits ledger is support
• Attach the master issue link in the description of this PR.
• Attach the google doc link if the BP is written in Google Doc.

Otherwise:

• Make sure the PR title is formatted like:
  <Issue #>: Description of pull request
e.g. Issue 123: Description ...
• Make sure tests pass via mvn clean apache-rat:check install spotbugs:check.
• Replace <Issue #> in the title with the actual Issue number.

---

[ca-simone-chiorazzo]

Hi @sijie, thanks for the quick review. How can I request other reviewers to take a look at this? I would move it forward quickly to solve a problem in our development environment. Thanks!

[eolivelli]

LGTM

[eolivelli]

@sijie so you think it is worth to cherry pick to 4.11 and cut a new RC? Or can we wait for 4.12? Hopefully we will release it within the end of November

[ca-simone-chiorazzo]

@sijie so you think it is worth to cherry pick to 4.11 and cut a new RC? Or can we wait for 4.12? Hopefully we will release it within the end of November

@sijie Sorry for the ping, could you please advice on this point? Honestly, for us, it would be better to have a new release with only this fix. Otherwise, we have to roll back the upgrade to python3.8 just for this sub-dependency. We cannot avoid it because we use pipenv to manage the dependencies

[zhavir]

Is there an ETA for this? It is a blocker also for us. Thanks

[eolivelli]

@zhavir I have merged this useful patch.

It will be available in 4.12.0 and in 4.11.2.
We don't have an estimate.

I can say that we are releasing 4.11.1 during this week, I expect 4.12.0 release within a month from today