Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/9034/
Test PASSed.

This seems to cause some issues, e.g., for our linting build in Travis.

How about we do something like what Celery does? E.g., they have the version string in celery/__init__.py

https://github.com/celery/celery/blob/9559045b8fd5cb4d6a99b02c39aff77ab537f234/celery/__init__.py#L17-L22

Then in setup.py they parse the celery/__init__.py and pull out the version.

https://github.com/celery/celery/blob/9559045b8fd5cb4d6a99b02c39aff77ab537f234/setup.py#L116-L129

Ours can be simpler though.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/9047/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/9048/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/9049/
Test PASSed.