You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/05 01:27:00 UTC

[jira] [Commented] (THRIFT-4275) Add support for zope.interface only, apart from twisted support.

    [ https://issues.apache.org/jira/browse/THRIFT-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153018#comment-16153018 ] 

ASF GitHub Bot commented on THRIFT-4275:
----------------------------------------

Github user jeking3 commented on the issue:

    https://github.com/apache/thrift/pull/1324
  
    @sunnypig just a reminder one thing was missed and needs to be updated - see my last comment, at the very least updating the command registration so the option appears in compiler help is mandatory - also recommend you rebase on master to get a clean build from CI.


> 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)