The biggest issue here is that pymgclient can essentially only be developed on Linux boxes. It shouldn't be too hard to change that, but there is always but. There is a bunch of similar logic to start Memgraph from Python in many different places: memgraph (e2e test), pymgclient, gqlalchemy (often repeated but slightly different for no reason).
The best solution would be to create a new library called, e.g., pymgutil and place the code there to start Memgraph with different options (native service, native binary, docker, etc.). NOTE: Don't try too hard and put the client logic there because then the circular deps come into place and that's not pretty.
The biggest issue here is that
pymgclientcan essentially only be developed on Linux boxes. It shouldn't be too hard to change that, but there is always but. There is a bunch of similar logic to start Memgraph from Python in many different places:memgraph(e2e test),pymgclient,gqlalchemy(often repeated but slightly different for no reason).The best solution would be to create a new library called, e.g.,
pymgutiland place the code there to start Memgraph with different options (native service, native binary, docker, etc.). NOTE: Don't try too hard and put the client logic there because then the circular deps come into place and that's not pretty.