Skip to content

Conversation

@mdumandag
Copy link
Contributor

It makes more sense to host API documentation and the long README
we have in Read the Docs so that they become more visible and
structured. Therefore, the long README is partitioned into chapters,
a small introduction(docs/index.rst) is created, and API documentation
is moved into a separate chapter. Also, API documentation of the
HazelcastClient is constructed as a top-level chapter since it is
generally the entry point for other documentation elements.

Finally, the README we have in Github is made shorter and
more descriptive. Also, added some badges to both README and
docs/index.rst to make users easily navigate between PyPI, Read the Docs,
and Github. The links to Read the Docs site (hazelcast.readthedocs.io)
won't work right now, but I will set up this once this is merged.

Closes #252

It makes more sense to host API documentation and the long README
we have in Read the Docs so that they become more visible and
structured. Therefore, the long README is partitioned into chapters,
a small introduction(docs/index.rst) is created, and API documentation
is moved into a separate chapter. Also, API documentation of the
HazelcastClient is constructed as a top-level chapter since it is
generally the entry point for other documentation elements.

Finally, the README we have in Github is made shorter and
more descriptive. Also, added some badges to both README and
docs/index.rst to make users easily navigate between PyPI, Read the Docs,
and Github. The links to Read the Docs site (hazelcast.readthedocs.io)
won't work right now, but I will set up this once this is merged.
@puzpuzpuz
Copy link

Left some comments, all nits.

@mdumandag
Copy link
Contributor Author

Thanks for the review Andrey

@mdumandag mdumandag merged commit 72af173 into hazelcast:master Dec 17, 2020
@mdumandag mdumandag deleted the rtd branch December 17, 2020 12:39
mdumandag added a commit to mdumandag/hazelcast-python-client that referenced this pull request Dec 18, 2020
As pointed out in the code review for hazelcast#266, there were
unnecessary newlines around the top-level callback function
definition, but we left it as it is since PEP8 recommends
such newlines.

Changed that part to use lambdas so that we can get rid of
the newlines.
mdumandag added a commit to mdumandag/hazelcast-python-client that referenced this pull request Dec 18, 2020
As pointed out in the code review for hazelcast#266, there were
unnecessary newlines around the top-level callback function
definition, but we left it as it is since PEP8 recommends
such newlines.

Changed that part to use lambdas so that we can get rid of
the newlines.
mdumandag added a commit that referenced this pull request Dec 18, 2020
As pointed out in the code review for #266, there were
unnecessary newlines around the top-level callback function
definition, but we left it as it is since PEP8 recommends
such newlines.

Changed that part to use lambdas so that we can get rid of
the newlines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Separate the README and the PyPI documentation

2 participants