Message154227
| Author |
tshepang |
| Recipients |
Ramchandra Apte, docs@python, eric.araujo, ezio.melotti, terry.reedy, tim.golden, tshepang |
| Date |
2012年02月25日.09:51:24 |
| SpamBayes Score |
1.2077092e-07 |
| Marked as misclassified |
No |
| Message-id |
<CAA77j2AE1ZMGuU3Bo_iVCL2R_puMrvq7-Z4gft7vza6zY7MYBA@mail.gmail.com> |
| In-reply-to |
<1330155336.29.0.86229641689.issue14112@psf.upfronthosting.co.za> |
| Content |
On Sat, Feb 25, 2012 at 09:35, Éric Araujo <report@bugs.python.org> wrote:
> What about this:
>
> All slice operations return a new list containing the requested elements. This
> -means that the following slice returns a shallow copy of the list *a*::
> +means that the following slice returns a shallow copy (see the documentation of
> +the :mod:`copy` module for a definition) of the list *a*::
That's kool, though I like Ezio's idea of putting it on a glossary
(and then linking to it) even more.
> (BTW, you can use syntax like Doc/tutorial/introduction.rst:487 to have links generated; see http://docs.python.org/devguide/triaging#generating-special-links-in-a-comment —also linked from the "Comment" label in the form, but it isn’t obvious that it’s a link).
Thanks for the pointer. Note however that I chose my approach because
it shows the info at a specific revision, in case the content changes
later on. |
|