[
https://issues.apache.org/jira/browse/MESOS-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854213#comment-15854213
]
Anthony Sottile commented on MESOS-5186:
----------------------------------------
[[email protected]]:
I'm no expert on protobuf but here's what I understand from the 2 projects I've
used it in and a small amount of research I've done:
The {{protobuf==3.x}} python library enables the following things:
- Compilation of the protobuf3 syntax
- Compatibility with python 3
- Backwards compatibility when compiling protobuf2 files
- Backwards compatibility when interacting with protobuf2 services
In short, it shouldn't be an issue -- the compiled files will continue to be
compiled from the protobuf2 syntax sources and produce a protubuf2 client
library. The client and server will continue to communicate with those.
> mesos.interface: Allow using protobuf 3.x
> -----------------------------------------
>
> Key: MESOS-5186
> URL: https://issues.apache.org/jira/browse/MESOS-5186
> Project: Mesos
> Issue Type: Improvement
> Components: python api
> Reporter: Myautsai PAN
> Assignee: Yong Tang
> Priority: Minor
> Labels: easyfix
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> We're working on integrating TensorFlow(https://www.tensorflow.org) with
> mesos. Both the two require {{protobuf}}. The python package
> {{mesos.interface}} requires {{protobuf>=2.6.1,<3}}, but {{tensorflow}}
> requires {{protobuf>=3.0.0}} . Though protobuf 3.x is not compatible with
> protobuf 2.x, but anyway we modify the {{setup.py}}
> (https://github.com/apache/mesos/blob/66cddaf/src/python/interface/setup.py.in#L29)
> from {{'install_requires': [ 'google-common>=0.0.1', 'protobuf>=2.6.1,<3'
> ],}} to {{'install_requires': [ 'google-common>=0.0.1', 'protobuf>=2.6.1' ],}}
> It works fine. Would you please consider support protobuf 3.x officially in
> the next release? Maybe just remove the {{,<3}} restriction is enough.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
