Py4J 0.2 Released

Py4J 0.2 has just been released. This is a significant milestone in the development of Py4J and the code no longer looks like a proof of concept. I worked a lot on the internal design while adding new features and simplifying existing ones. Look at the changelog for more details.

2 thoughts on “Py4J 0.2 Released”

  1. Hi.
    I find this project interesting as currently there are no many choices for calling java from pyhton. The best I know is execnet connecting CPython and Jython. But Py4J seems more natural and can be faster.

    I see in sources that a custom text protocol is used implemented in oo-way. For performance and millions of method calls (such usages I have in mind) probably a binary optimized protocol will be much better. It can be easy to use as there is Google Protocol Buffers and similar.

    But I don’t know if performance is important to you and in what direction you want to go.

    1. A binary protocol makes a lot of sense. Using protobuf was on my todo list, but I wanted to prioritize certain features first (mapping Java collections to Python collections, smarter conversion of Python calls to Java calls). Now that this is done, I’m trying to implement callbacks (e.g., so that Java programs can call Python objects) and I realize that I’ll probably expand the protocol. It might be smarter to look at Protobuf now. Thanks for your comment!

Leave a Reply

Your email address will not be published. Required fields are marked *