chore(cd): fix protobuf import issue

[joshua-goldstein]

Problem

Currently, calling import pydgraph will complain because of module import path issues. E.g.,

>>> import pydgraph
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/manas/.local/lib/python3.10/site-packages/pydgraph/__init__.py", line 17, in <module>
    from pydgraph.client_stub import *
  File "/home/manas/.local/lib/python3.10/site-packages/pydgraph/client_stub.py", line 20, in <module>
    from pydgraph.proto import api_pb2_grpc as api_grpc
  File "/home/manas/.local/lib/python3.10/site-packages/pydgraph/proto/api_pb2_grpc.py", line 5, in <module>
    import api_pb2 as api__pb2

This is not a new problem with protobufs. See e.g. [1] [2] [3] [4][5]. Essentially, the issue has to do with the generated protobuf files, which make an import which is not by default discoverable. One trick was to use a relative import path, but this is not a great solution and may be causing issues.

Solution

Use __init__.py in the protos package to add the parent directory to the Python path, so that the package will be discovered. This means we no longer have to modify the generated protobuf files.

[mangalaman93]

This is cool, good work on figuring this out. We should do a rc release on Pypi before the actual release and make sure pull and import works as expected.

[MichelDiz]

I had this problem and had to downgrade.

[mangalaman93]

I had this problem and had to downgrade.

What do you mean? I assumed that the import was working for the new release

[MichelDiz]

I had this problem and had to downgrade.

What do you mean? I assumed that the import was working for the new release

Yeah, for some reason it happened to me. I was creating a new cron job(like 1 an half day ago) to delete old data in the telemetry code.
I use Python for that. I got the same error for api__pb2. And I was confused. So I downgraded and everything worked fine again.

[joshua-goldstein]

@MichelDiz When you have a moment could you try to pull pip install pydgraph==23.0.1rc1? This PR should resolve these issues. If yes, please approve #205 .