Hi Stefan,

I've also been waiting for someone to look at my pull request
https://github.com/boostorg/python/pull/8
(well, I may be too patient). It would be really nice if something would eventually happen.

Best regards
Ulli

Am 02.02.2015 um 19:49 schrieb Stefan Seefeld:
Axel,

I'm trying to look into the open patches to see whether I can help
shrink the list of open issues. The issues / patches I have seen from
you all look minor / sensible, so I hope I can merge them soon. Still
trying to get back up-to-speed with the boost build and test processes etc.

I'm subscribed to both the c++-sig as well as the boost mailing lists. I
think the former might be slightly better to discuss boost.python
issues, if only for the higher SNR.

FWIW,
         Stefan

On 02/02/15 01:43 PM, Huebl, Axel wrote:
Hm, the language binding is dead and 404
   http://sourceforge.net/p/boost/mailman/boost-langbinding/

Has anyone an idea about my question? :)

Best,
Axel
On 28.01.2015 15:21, Huebl, Axel wrote:
Oh I just realized
   boost-langbinding

is the better place to report this.

Sry for cross-posting, I will migrate my question there.


Best,
Axel

On 28.01.2015 15:01, Huebl, Axel wrote:
Hi,

I was directed here from the Boost groups homepage
   http://www.boost.org/community/groups.html#cplussig

so I hope my question is well placed.

I was wondering if, how and when patches for Boost.Python (specially bug
fixes) are merged.

When I reported two bugs (including patches) beginning of the month
(that sounds a bit impatient - so if I am just pushing to much just tell
me) in both trac and on GitHub:
   https://svn.boost.org/trac/boost/ticket/10932
   https://svn.boost.org/trac/boost/ticket/10933

I noticed that there are other pull requests since at least two boost
stable releases on GitHub
   https://github.com/boostorg/python/pulls
   (some of them also with a trac issue)

that have not yet been reviewed/included/commented-on/closed in the code
base even if they are most of the time straight forward fixes.

My background:
   I am combined Boost.Python with via cmake with an open source, (mpi)
parallel, many-GPGPU code [1] compiled with nvcc 6.5 and noted some
minor compile errors in Boost.Python that can be fixed quite easily.

(Btw: it works like a charm, thank you so much!)


Best regards,
Axel Huebl

[1] http://picongpu.hzdr.de



_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/listinfo/cplusplus-sig



_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/listinfo/cplusplus-sig


_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
https://mail.python.org/mailman/listinfo/cplusplus-sig

Reply via email to