Kshitij, > Many thanks for the suggestions; I have started working on that. I just > checked the accepted proposals for this year and it seems that no one will > be working on Python bindings. If you like, I would be interested in > continuing the work. I believe, I will need guidance for that. Currently, > I am a bit engaged with two other projects which have upcoming deadlines > in the next month and I hope to complete them in the next few weeks. > Subsequently, I will be able to resume working on the Python bindings. I > hope this is suitable. > > Looking forward to hearing from you.
It is absolutely possible (and highly appreciated if you did) to work on this. Nobody is currently looking into creating Python bindings for HPX, so it would be completely up to you to move that forward at this point. Please feel free to ask more questions here once you start working on it. BTW: here is a library which looks quite suitable for this: https://github.com/pybind/pybind11. It is more modern than the venerable Boost.Python library while exposing a very similar interface to the user. The license would be compatible with ours as well... Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > Vielen Dank > Kshitij Kumar > > On Sun, Apr 17, 2016 at 5:56 PM, Hartmut Kaiser <[email protected]> > wrote: > Kshitij, > > > I had submitted a proposal earlier for the development of Python > bindings > > and just wanted to provide some updates. I have been working with some > hpx > > examples, going through the documentation and also looking at the Python > > bindings created for other libraries. Additionally, I have also spent > some > > time and gained the initial familiarity with Boost.Python library. I > > intend to continue with the development of some function bindings, for a > > use case, in a day or two. > > Wow, great! > > > I would be grateful for your suggestions in > > this regard. You can let me know if there are certain aspects which I > need > > to address first. > > Getting HPX running and stopping is probably the first thing you want to > do. Perhaps something like: > > > import sys > import HPX > > def hpx_main(argv): > print 'Hello HPX world!' > return HPX.finalize() > > def main(argv): > return HPX.init(hpx_main, argv) > > if __name__ == "__main__": > sys.exit(main(sys.argv)) > > > Later on we can try finding more 'pythonic' abstractions, but this > functionality would be needed in any case. > > Regards Hartmut > --------------- > http://boost-spirit.com > http://stellar.cct.lsu.edu > > _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
