Add Python Bindings Appendix

[rhc54]

Create the C <-> Python datatype correspondence table.
Provide Python-language definitions for all C-level interfaces.

Fix minor typos in server module function descriptions

Signed-off-by: Ralph Castain [email protected]

[rhc54]

@jjhursey See what you think of the table

[rhc54]

@pmrich @dsikich Please take a look

[rhc54]

Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.

* You do not need to vote on every proposal
* If you have no opinion, don't vote - that is also useful data
* If you've already commented on this issue, please still vote so
      we know your current thoughts
* Not all proposals solve exactly the same problem, so we may end
      up accepting proposals that appear to have some overlap

This is not a binding majority-rule vote, but it will be a very
significant input into the corresponding ASC decision.

Here are the meanings for the emojis:

* Hooray or Rocket: I support this so strongly that I
      want to be an advocate for it
* Heart: I think this is an ideal solution
* Thumbs up: I'd be happy with this solution
* Confused: I'd rather we not do this, but I can tolerate it
* Thumbs down: I'd be actively unhappy, and may even consider
      other technologies instead

If you want to explain in more detail, feel free to add another
comment, but please also vote on this comment.

[jjhursey]

This looks good. I think an example would be helpful for the datatypes. Maybe a small C vs small Python PMix program that uses types.

[rhc54]

@jjhursey See example 😄

[jjhursey]

Thanks. That example helps!

[SteVwonder]

I'm assuming that the plan is to only support Python 3 and not support Python 2? If so, several of my inline comments are irrelevant. Either way, it is probably worth noting in the text that the types specified are assumed to be Python 3 types (i.e., 'string' means Python 3's 'str' and not Python 2's str).

[rhc54]

I'm assuming that the plan is to only support Python 3 and not support Python 2? If so, several of my inline comments are irrelevant. Either way, it is probably worth noting in the text that the types specified are assumed to be Python 3 types (i.e., 'string' means Python 3's 'str' and not Python 2's str).

Argonne only wants Python 3 support - I’ll note that in the introduction