Closed jmao-denver closed 3 years ago
The stated goal of the epic is to make the server side Python integration (the deephaven package) much more Pythonic, thus providing a better experience to the Python developers. A parallel goal is to make it as seamless as possible for a client side Python script to run on the server and vice versa. The latter requires we have an identical or very similar design of the Python API on both the server and the client.
After having carefully examining the current implementation of Python integration on the server side, I have come to realize that the scope of the work is quite a bit bigger than I first thought. These are the main reasons behind that realization. Some of these reasons especially 1, 2, also argue strongly against a partial effort.
@rcaudy reviewed the comments and agreed with most of them. The parent epic will be my next big priority. As this is going to be a long project, we will need to break the epic into properly sized deliverables. More tickets are coming.
The core class in DH/PY integration is Table, it is used both in output and input in many of the sub-modules. This means wrapping it to make it more Pythonic could be a breaking change for the depending sub-modules without rewriting everything. We need to find out for sure if that's the case.
under Epic #1263