{"action":"created","issue":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/527","repository_url":"https://api.github.com/repos/flux-framework/flux-core","labels_url":"https://api.github.com/repos/flux-framework/flux-core/issues/527/labels{/name}","comments_url":"https://api.github.com/repos/flux-framework/flux-core/issues/527/comments","events_url":"https://api.github.com/repos/flux-framework/flux-core/issues/527/events","html_url":"https://github.com/flux-framework/flux-core/issues/527","id":129897390,"number":527,"title":"consider flux-python-binding project","user":{"login":"garlick","id":169947,"avatar_url":"https://avatars.githubusercontent.com/u/169947?v=3","gravatar_id":"","url":"https://api.github.com/users/garlick","html_url":"https://github.com/garlick","followers_url":"https://api.github.com/users/garlick/followers","following_url":"https://api.github.com/users/garlick/following{/other_user}","gists_url":"https://api.github.com/users/garlick/gists{/gist_id}","starred_url":"https://api.github.com/users/garlick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garlick/subscriptions","organizations_url":"https://api.github.com/users/garlick/orgs","repos_url":"https://api.github.com/users/garlick/repos","events_url":"https://api.github.com/users/garlick/events{/privacy}","received_events_url":"https://api.github.com/users/garlick/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-01-29T22:15:56Z","updated_at":"2016-02-10T21:22:50Z","closed_at":null,"body":"I wanted to float the idea of splitting the python bindings out of core.\r\n\r\nThere are two pain points resulting from having it in:\r\n* python bindings have to track iterative flux-core api evolution\r\n* when make check runs, python tests are the first ones that launch a comms session, so any disruption during development is first detected as a python binding failure, a little harder to run down than if we hit that in the early sharness tests.\r\n\r\nNow that flux-core releases are being tagged, if we pulled the python bindings out, we could update them on the flux-core release cycle rather than as we go.\r\n\r\nI think the bindings can be generated from the installed header files, i.e. access to flux-core source would not be a requirement?\r\n\r\nA downside is that `flux-list-instances` and `flux-lstopo` would also need to be relocated.\r\n\r\nI know we discussed this at length when these went in and arrived at the current situation.  I may not remember all the reasons, but have we moved into a different phase of the project where the argument may have shifted somewhat?"},"comment":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/comments/182587522","html_url":"https://github.com/flux-framework/flux-core/issues/527#issuecomment-182587522","issue_url":"https://api.github.com/repos/flux-framework/flux-core/issues/527","id":182587522,"user":{"login":"trws","id":660149,"avatar_url":"https://avatars.githubusercontent.com/u/660149?v=3","gravatar_id":"","url":"https://api.github.com/users/trws","html_url":"https://github.com/trws","followers_url":"https://api.github.com/users/trws/followers","following_url":"https://api.github.com/users/trws/following{/other_user}","gists_url":"https://api.github.com/users/trws/gists{/gist_id}","starred_url":"https://api.github.com/users/trws/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trws/subscriptions","organizations_url":"https://api.github.com/users/trws/orgs","repos_url":"https://api.github.com/users/trws/repos","events_url":"https://api.github.com/users/trws/events{/privacy}","received_events_url":"https://api.github.com/users/trws/received_events","type":"User","site_admin":false},"created_at":"2016-02-10T21:22:50Z","updated_at":"2016-02-10T21:22:50Z","body":"It would take some refactoring, but probably just a couple of hours of concentrated work.  I'll check into it and see if I can make that change."}}