[
https://issues.apache.org/jira/browse/MESOS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119530#comment-14119530
]
Till Toenshoff commented on MESOS-1750:
---------------------------------------
That was exactly the only solution I could come up with so far as well;
patching the python proto results after they have been rendered. Not really
beautiful solution but maybe the only option we got other than changing the
proto locations which seems just wrong considering that we would have to mix
all proto-files into one flat folder (including the internal proto's for
allowing MESOS-1731 to happen).
> 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)
