Re: Python docstrings and licensing/authorship

2020-09-17 Thread John Snow
On 9/17/20 8:55 AM, Markus Armbruster wrote: Daniel P. Berrangé writes: On Wed, Sep 16, 2020 at 12:22:37PM -0400, John Snow wrote: [...] The real question I have is if anyone thinks it would be "rude" to separate out any of the comment preambles (currently not visible at runtime or docs in a

Re: Python docstrings and licensing/authorship

2020-09-17 Thread Markus Armbruster
Daniel P. Berrangé writes: > On Wed, Sep 16, 2020 at 12:22:37PM -0400, John Snow wrote: [...] >> The real question I have is if anyone thinks it would be "rude" to separate >> out any of the comment preambles (currently not visible at runtime or docs >> in any way, shape or form!) into two pieces

Re: Python docstrings and licensing/authorship

2020-09-16 Thread Daniel P . Berrangé
On Wed, Sep 16, 2020 at 12:22:37PM -0400, John Snow wrote: > On 9/16/20 12:05 PM, Christophe de Dinechin wrote: > > > > > > > On 16 Sep 2020, at 17:47, John Snow wrote: > > > > > > For some of the Python cleanup work I am doing, I am moving preamble > > > comments into docstrings. These docstr

Re: Python docstrings and licensing/authorship

2020-09-16 Thread John Snow
On 9/16/20 12:05 PM, Christophe de Dinechin wrote: On 16 Sep 2020, at 17:47, John Snow wrote: For some of the Python cleanup work I am doing, I am moving preamble comments into docstrings. These docstrings are visible in interactive editors and may be visible when using Sphinx to generate

Re: Python docstrings and licensing/authorship

2020-09-16 Thread Christophe de Dinechin
> On 16 Sep 2020, at 17:47, John Snow wrote: > > For some of the Python cleanup work I am doing, I am moving preamble comments > into docstrings. These docstrings are visible in interactive editors and may > be visible when using Sphinx to generate documentation manuals for Python > code. >