From jvansanten at gmail.com Fri Apr 12 15:48:58 2024 From: jvansanten at gmail.com (Jakob van Santen) Date: Fri, 12 Apr 2024 21:48:58 +0200 Subject: [C++-sig] Emitting complete type information in boost-python docstrings Message-ID: <4D837306-568F-4B41-8523-C497FF0A5204@gmail.com> Hello, I?m not sure if this is the right forum for this question (it?s been pretty quiet here lately), but here goes: I have been working on generating PEP 484 type stubs for a large legacy codebase that is heavily tied to boost-python. This required some modifications to boost-python itself in order to get complete type information into the generated docstrings, where it can be consumed by external tooling to generate stubs: https://github.com/boostorg/python/pull/417 I have found this quite useful, and suspect it might be useful for others as well to have it in a Boost release. Can anyone give me a pointer as to how to make that happen, or let me know where I should be asking instead? Thanks! Cheers, Jakob -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel at cadext.com Sat Apr 13 19:30:33 2024 From: daniel at cadext.com (daniel marcotte) Date: Sun, 14 Apr 2024 07:30:33 +0800 Subject: [C++-sig] Cplusplus-sig Digest, Vol 139, Issue 1 In-Reply-To: References: Message-ID: This would be huge for me! I?ve been adding tags to my user docstrings and generating stub files in python with inspect With the tags, I can emit @overload @staticmethod .etc., but some work is done by hand that leaves room for error On Sun, Apr 14, 2024 at 12:00?AM wrote: > Send Cplusplus-sig mailing list submissions to > cplusplus-sig at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/cplusplus-sig > or, via email, send a message with subject or body 'help' to > cplusplus-sig-request at python.org > > You can reach the person managing the list at > cplusplus-sig-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cplusplus-sig digest..." > > > Today's Topics: > > 1. Emitting complete type information in boost-python docstrings > (Jakob van Santen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 12 Apr 2024 21:48:58 +0200 > From: Jakob van Santen > To: cplusplus-sig at python.org > Subject: [C++-sig] Emitting complete type information in boost-python > docstrings > Message-ID: <4D837306-568F-4B41-8523-C497FF0A5204 at gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I?m not sure if this is the right forum for this question (it?s been > pretty quiet here lately), but here goes: > > I have been working on generating PEP 484 type stubs for a large legacy > codebase that is heavily tied to boost-python. This required some > modifications to boost-python itself in order to get complete type > information into the generated docstrings, where it can be consumed by > external tooling to generate stubs: > > https://github.com/boostorg/python/pull/417 > > I have found this quite useful, and suspect it might be useful for others > as well to have it in a Boost release. Can anyone give me a pointer as to > how to make that happen, or let me know where I should be asking instead? > Thanks! > > Cheers, > Jakob > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://mail.python.org/pipermail/cplusplus-sig/attachments/20240412/14bf01ad/attachment-0001.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Cplusplus-sig mailing list > Cplusplus-sig at python.org > https://mail.python.org/mailman/listinfo/cplusplus-sig > > > ------------------------------ > > End of Cplusplus-sig Digest, Vol 139, Issue 1 > ********************************************* > -------------- next part -------------- An HTML attachment was scrubbed... URL: