Message260526
Another reason to value the status-quo in this case is that this isn't just
a matter for the Python documentation; it's about the recommended usage for
the markup, which is used by many other packages.
Questions that should be discussed include:
1. Should we clarify the documentation for the current annotations to
the intended use is more consistently understood, or should we leave
it as-is?
2. Are other distinct kinds of annotations (such as per-parameter notes)
needed?
If so, we'll need to consider specific reader / information-content
needs and determine how they should be marked using new constructs.
This is independent of implementation, which is likely straightforward. |
|
Date |
User |
Action |
Args |
2016-02-19 17:37:14 | fdrake | set | recipients:
+ fdrake, georg.brandl, ezio.melotti, docs@python, berker.peksag, martin.panter, Tony R. |
2016-02-19 17:37:14 | fdrake | set | messageid: <1455903434.77.0.47072571677.issue26366@psf.upfronthosting.co.za> |
2016-02-19 17:37:14 | fdrake | link | issue26366 messages |
2016-02-19 17:37:14 | fdrake | create | |
|