[
https://issues.apache.org/jira/browse/THRIFT-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156381#comment-16156381
]
ASF GitHub Bot commented on THRIFT-4275:
----------------------------------------
Github user sunnypig commented on the issue:
https://github.com/apache/thrift/pull/1324
Sorry for my belated rely. I have just updated the registration. However,
I have no idea on how to add a proper unit test, since I can't find any test
code for the option of "py:twisted" which perhaps can be taken for a reference.
> Add support for zope.interface only, apart from twisted support.
> ----------------------------------------------------------------
>
> Key: THRIFT-4275
> URL: https://issues.apache.org/jira/browse/THRIFT-4275
> Project: Thrift
> Issue Type: Wish
> Components: Python - Compiler
> Reporter: Charlie Zhang
> Priority: Trivial
> Labels: features
>
> Since twisted depends on zope.interface, each interface we defined in thrift
> file will be generated as a class derived from zope.interface if py:twisted
> option is enabled. This is great because we can treat implementations of
> these interfaces as components which can be registered in zope.component.
> However, sometimes we just only want to benefit from Component Object Model
> programming which is provided by the combination of zope.interface,
> zope.component and even zope.configuration, but not the deferred mechanism
> in twisted. So, besides option py:twisted, shall we add an extra option
> py:zope.interface ?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
