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
-- 

Axel Huebl
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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

Reply via email to