On Fri, Feb 4, 2011 at 6:42 AM, Andrew Francis <span dir="ltr"><<a href="mailto:andrewfr_ice@yahoo.com">andrewfr_ice@yahoo.com</a>></span> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">>sieve of erathosthenes, both sound more academic than practical to me.<br>
>However, you're more onto what can be explained by each than me, so if you<br>
>think you can incorporate them in a suitable way that demonstrates >something usefully.. then by all means do it and make a patch.<br>
<br>
</div>The sieve doesn't need a patch to Stackless. It is just an example. The sieve is useful because many languages with channels like to show how the sieve can be solved in a terse manner. The sieve example I have is useful because I altered it to support pickling.<br>

<div class="im"><br></div></blockquote><div><br></div><div>The Python documentation, and by extension the Stackless documentation which builds on it, is written in reStructuredText. See the following link..</div><div><br>
</div><div> <a href="http://svn.python.org/view/stackless/branches/release27-maint/Doc/library/stackless/">http://svn.python.org/view/stackless/branches/release27-maint/Doc/library/stackless/</a></div><div><br></div><div>
<a href="http://svn.python.org/view/stackless/branches/release27-maint/Doc/library/stackless/"></a>So the patch I was referring to, is the way in which you would provide any changes to the existing documentation files, or add new ones.</div>
<div><br></div><div>Hope that is clearer. :-)</div><div><br></div><div>Cheers,</div><div>Richard.</div></div>