<br><br><div class="gmail_quote">On Thu, Feb 4, 2010 at 00:57, anatoly techtonik <span dir="ltr"><<a href="mailto:techtonik@gmail.com">techtonik@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Greetings,<br>
<br>
I'm writing a module for current Python 2.6 and I would like to<br>
reference documentation for Python 2.6, because I am not sure if<br>
behavior won't be changed in further series. So far I can link only<br>
to:<br>
<br>
<a href="http://docs.python.org/" target="_blank">http://docs.python.org/</a> (stable, 2.6)<br>
<a href="http://docs.python.org/dev/" target="_blank">http://docs.python.org/dev/</a> (2.7)<br>
<a href="http://docs.python.org/dev/py3k/" target="_blank">http://docs.python.org/dev/py3k/</a><br>
<br>
When stable changes to 2.7 my reference will point to the different<br>
version than I was meant when writing comment. It is possible to link<br>
to docs for minor 2.6.4 <a href="http://www.python.org/doc/2.6.4/" target="_blank">http://www.python.org/doc/2.6.4/</a> but I would<br>
like to link to latest version of docs in 2.6 branch that may not yet<br>
found way into official minor release.<br><font class="Apple-style-span" color="#888888"><br></font></blockquote><div><br></div><div>As you said, something in 2.6 could change, so linking to a 2.6.x doc link instead of a specific version could be misleading in your docs if a change did occur that you were not aware about.</div>
<div><br></div><div>But since micro releases rarely have anything change in them you should be able to link to practically any release and feel comfortable in knowing that things should stay the same through all of 2.6.x.</div>
<div><br></div><div>-Brett </div></div>