RE: [Docstring-develop] DPS - possible bugs/features

[Tony J I. (Tibs) <to...@ls...>]

David Goodger wrote:
> [Tony]
> > First, I've uploaded a new pydps
>
> Great; I'll have to take a look at it. Where should it be installed on
> the source tree? (Perhaps a short README.txt file?)

At the moment, it doesn't need to be anywhere particular - it just
imports things from DPS and restructuredtext (easy if they've been
installed). I'll try to coin a README.txt file sometime soon, since this
thing begins to approach usability (hah, until I restructure it under
the new scheme!)

> [Tony]
> > 2. When processing the string module (yes, I know it isn't marked as
> >    containing reST texts!), the text::
> >
> >        [1:2]
> >
> >    (or similar) is incorrectly identified as a link. Not a
> Good Thing.
>
> ``1:2`` won't be a link (as your example confirms), but ``a:b`` will
> be. Why? Because according to RFC2396, 'a' could be a URI scheme (as
> in 'http' or 'mailto'). The solution? Use inline literals.

Hmm. Will `a:b` be treated as a URI? (I haven't tested it).

Is ``a:b`` *really* likely to be a sensible URI, given that ``a`` is
entirely "local"? Should we be treating with the whole possible gamut of
URIs, or restricting ourselves to those most likely? And other exciting
questions I shall try not to think too hard about for the moment...

Tibs

--
Tony J Ibbs (Tibs)      http://www.tibsnjoan.co.uk/
Give a pedant an inch and they'll take 25.4mm
(once they've established you're talking a post-1959 inch, of course)
My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.)