You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/09/07 04:21:00 UTC

[jira] [Assigned] (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:all-tabpanel ]

James E. King, III reassigned THRIFT-4275:
------------------------------------------

    Assignee: James E. King, III

> 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
>    Affects Versions: 0.10.0
>            Reporter: Charlie Zhang
>            Assignee: James E. King, III
>            Priority: Trivial
>              Labels: features
>             Fix For: 0.11.0
>
>
> 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)