[
https://issues.apache.org/jira/browse/THRIFT-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278579#comment-13278579
]
Hudson commented on THRIFT-1539:
--------------------------------
Integrated in Thrift #474 (See [https://builds.apache.org/job/Thrift/474/])
THRIFT-1539:Build and distribute the fb303 python libraries along with
thrift
Client: contrib/fb303 - py
Patch: Jake Farrell
Updated build file so dist egg will include project headers, will publish with
py client lib to pypi as part of release process. (Revision 1339967)
Result = ABORTED
jfarrell : http://svn.apache.org/viewvc/?view=rev&rev=1339967
Files :
* /thrift/trunk/contrib/fb303/py/setup.py
> Build and distribute the fb303 python libraries along with thrift
> -----------------------------------------------------------------
>
> Key: THRIFT-1539
> URL: https://issues.apache.org/jira/browse/THRIFT-1539
> Project: Thrift
> Issue Type: Wish
> Components: Build Process, Deployment, Python - Library
> Reporter: Morten Lied Johansen
> Assignee: Jake Farrell
> Fix For: 0.9
>
> Attachments: THRIFT-1539.patch
>
>
> [Scribe|https://github.com/facebook/scribe], which is another project open
> sourced by Facebook, depends on fb303 which is hidden away in the contrib
> directory of Thrift. If the fb303 library could be uploaded to PyPI along
> with the thrift library, it would be a lot easier to build and install
> Scribe. This might also be relevant to do for all languages that distribute
> libraries used by generated code, not just Python.
> As far as I understand it, the fb303 library defines a useful API for long
> running services in general, so if it was distributed better, it might get a
> decent user base over time.
> PS.
> Yes, it seems silly that the Thrift project should maintain and distribute a
> library mostly (only?) used by a different, completely independent, project,
> but that's how Facebook decided to do it when they open sourced these
> things...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
