thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (THRIFT-4275) Add support for zope.interface only, apart from twisted support.
Date Thu, 03 Aug 2017 07:39:00 GMT


ASF GitHub Bot commented on THRIFT-4275:

GitHub user sunnypig opened a pull request:


    add support for zope.interface only (excluding support for twisted) in python compiler

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1324


> Add support for zope.interface only, apart from twisted support.
> ----------------------------------------------------------------
>                 Key: THRIFT-4275
>                 URL:
>             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

View raw message