[
https://issues.apache.org/jira/browse/MESOS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116911#comment-14116911
]
Till Toenshoff commented on MESOS-1750:
---------------------------------------
{{containerizer.proto}} imports from {{"mesos/mesos.proto"}}, so the resulting
python code in {{containerizer_pb2.py}} tries to import from
{{mesos.mesos_pb2}} where it should actually import from {{mesos_pb2}}.
It seems as if the translation of the original structure into the flat
interface structure is prone to cause issues with proto's that import from
other mesos proto's while qualifying their relative path.
> ImportError in containerizer_pb2.py
> -----------------------------------
>
> Key: MESOS-1750
> URL: https://issues.apache.org/jira/browse/MESOS-1750
> Project: Mesos
> Issue Type: Bug
> Components: python api
> Reporter: Till Toenshoff
> Labels: mesos.interface, python-egg
>
> It appears as if the split of the Python egg (native/interface/protocol) has
> introduced a new issue.
> Whenever I am trying to use {{from mesos.interface import
> containerizer_pb2}}, I am receiving an {{ImportError: No module named
> mesos_pb2}}.
> For replicating this issue, try running
> {{"build/src/examples/python/test-containerizer"}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
