moved packaging chapter after case-study chapter, fixed index/TOC/navigation. 'I know, I'll just manage the navigation stuff manually,' I said. 'How often am I going to rearrange chapters?' I said.

case-study-porting-chardet-to-python-3.html

@@ -5,7 +5,7 @@
 <!--[if IE]><script src=j/html5.js></script><![endif]-->
 <link rel=stylesheet href=dip3.css>
 <style>
-body{counter-reset:h1 17}
+body{counter-reset:h1 16}
 ins,del{line-height:2.154;text-decoration:none;font-style:normal;display:inline-block;width:100%}
 ins{background:#9f9}
 del{background:#f87}
@@ -818,7 +818,7 @@ tests\EUC-JP\arclamp.jp.xml                                  EUC-JP with confide
 <li>Test cases are essential. Don&#8217;t port anything without them. The <em>only</em> reason I have any confidence that <code>chardet</code> works in Python 3 is that I started with a test suite that exercised all major code paths. If you don&#8217;t have any tests, write some tests before you start porting to Python 3. If you have a few tests, write more. If you have a lot of tests, then the real fun can begin.
 </ol>
 
-<p class=v><a rel=prev href=packaging.html title='back to &#8220;Packaging Python Libraries&#8221;'><span class=u>&#x261C;</span></a> <a rel=next href=where-to-go-from-here.html title='onward to &#8220;Where to Go From Here&#8221;'><span class=u>&#x261E;</span></a>
+<p class=v><a rel=prev href=multiprocessing.html title='back to &#8220;Threading &amp; Multiprocessing&#8221;'><span class=u>&#x261C;</span></a> <a rel=next href=packaging.html title='onward to &#8220;Packaging Python Libraries&#8221;'><span class=u>&#x261E;</span></a>
 <p class=c>&copy; 2001&ndash;9 <a href=about.html>Mark Pilgrim</a>
 <script src=j/jquery.js></script>
 <script src=j/prettify.js></script>