No subject
Sun Apr 26 06:47:01 MDT 2009
docutisl "Parser" object, which could read the Lore sources and translate it
into a "doctree" of nodes. From there you could generate the output in
whatever format is supported by docutils. This would be doable in theory,
but I don't think it would be trivial or even easy, and then you'd have
another tool to maintain until the end of time.
Sphinx adds a bunch of extensions and conventions on top of docutils proper,
and I have little to no idea of what would be involved in handling those
issues.
> >
> >> - Foolscap 0.5 was released today, which made me wonder what they
> >>use for
> >> docs...and it's Lore. I brought this up on IRC, and it was
> >>suggested
> >> by many that Lore should stick around even after the conversion
> >>according
> >> to the standard Twisted compatibility policy, to give anyone who
> >>still
> >> uses it time to migrate. This sounds like a fine idea to me.
> >> Any thoughts?
> >
> >Since nobody really uses lore's API, the same compatibility policy
> >doesn't really apply. In lore's case, I would say that the policy
> >should be that we include it with X more releases just for packaging
> >convenience, but stop doing maintenance immediately.
>
> As long as someone wants to do maintenance, I don't see any reason to
> stop them from doing it. We might mark all the Lore tickets lowest
> priority or otherwise signal that some subset of the "core" developers
> aren't interested in maintaining it.... but then, how would that be any
> different from the status quo?
>
> Jean-Paul
>
>
If someone wants to maintain Lore, I certainly have no objection, but I
don't think anyone really does. And it's not like it won't still be in the
SVN repos back in the history someplace, even if it were to be "removed"
from trunk.
I don't have strong feelings about it either way, but my feeling is Lore
should maybe be officially deprecated for a release (or 2, 3, etc.) and then
"removed" from trunk, and if someone wants to maintain it themselves, they
can fork it and deal with it outside the Twisted project. Or it can be
"resurrected" later on if someone wants. At the very least, don't force
users to install Lore along with the rest of Twisted once Lore is out of
general use. Maybe it could be a separate package like web2?
But if it were just up to me, I would just get rid of it, to avoid taking up
developer time, cluttering up trac with open tickets, etc.
Kevin Horn
--000e0cd6eeba77a29f047dafcbd0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">On Thu, Jan 21, 2010 at 3:03 AM, <span dir=3D"l=
tr"><<a href=3D"mailto:exarkun at twistedmatrix.com">exarkun at twistedmatrix.=
com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"bor=
der-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-=
left: 1ex;">
<br>
On IRC last night I brought up the idea that we could skip the<br>
conversion to ReST and use Sphinx with xhtml input documents. =A0The<br>
conclusion seemed to be that this might be difficult, but no one was<br>
really sure what work would be involved in this approach. =A0Kevin's<br=
>
already put a lot of effort into the conversion. =A0It would be nice if<br>
someone else could investigate this.<br></blockquote><div><br>From a docuti=
ls point of view, I _think_ it would involve creating a docutisl "Pars=
er" object, which could read the Lore sources and translate it into a =
"doctree" of nodes.=A0 From there you could generate the output i=
n whatever format is supported by docutils.=A0 This would be doable in theo=
ry, but I don't think it would be trivial or even easy, and then you=
9;d have another tool to maintain until the end of time.<br>
<br>Sphinx adds a bunch of extensions and conventions on top of docutils pr=
oper, and I have little to no idea of what would be involved in handling th=
ose issues.<br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"bord=
er-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-l=
eft: 1ex;">
<div class=3D"im">><br>
>> =A0 - Foolscap 0.5 was released today, which made me wonder what t=
hey<br>
>>use for<br>
>> =A0 =A0 docs...and it's Lore. =A0I brought this up on IRC, and=
it was<br>
>>suggested<br>
>> =A0 =A0 by many that Lore should stick around even after the conve=
rsion<br>
>>according<br>
>> =A0 =A0 to the standard Twisted compatibility policy, to give anyo=
ne who<br>
>>still<br>
>> =A0 =A0 uses it time to migrate. =A0This sounds like a fine idea t=
o me.<br>
>> =A0 =A0 Any thoughts?<br>
><br>
>Since nobody really uses lore's API, the same compatibility policy<=
br>
>doesn't really apply. =A0In lore's case, I would say that the p=
olicy<br>
>should be that we include it with X more releases just for packaging<br=
>
>convenience, but stop doing maintenance immediately.<br>
<br>
</div>As long as someone wants to do maintenance, I don't see any reaso=
n to<br>
stop them from doing it. =A0We might mark all the Lore tickets lowest<br>
priority or otherwise signal that some subset of the "core" devel=
opers<br>
aren't interested in maintaining it.... but then, how would that be any=
<br>
different from the status quo?<br>
<br>
Jean-Paul<br>
<br></blockquote></div><br>If someone wants to maintain Lore, I certainly h=
ave no objection, but I don't think anyone really does.=A0 And it's=
not like it won't still be in the SVN repos back in the history somepl=
ace, even if it were to be "removed" from trunk.<br>
<br>I don't have strong feelings about it either way, but my feeling is=
Lore should maybe be officially deprecated for a release (or 2, 3, etc.) a=
nd then "removed" from trunk, and if someone wants to maintain it=
themselves, they can fork it and deal with it outside the Twisted project.=
=A0 Or it can be "resurrected" later on if someone wants.=A0 At t=
he very least, don't force users to install Lore along with the rest of=
Twisted once Lore is out of general use.=A0 Maybe it could be a separate p=
ackage like web2?<br>
<br>But if it were just up to me, I would just get rid of it, to avoid taki=
ng up developer time, cluttering up trac with open tickets, etc.<br><br>Kev=
in Horn<br>
--000e0cd6eeba77a29f047dafcbd0--
More information about the Twisted-Python
mailing list