Remove most references to urllib2 from docs
Upgrading of request objects still not addressed.
diff --git a/doc.html.in b/doc.html.in
index 28a66f4..e84ccd8 100644
--- a/doc.html.in
+++ b/doc.html.in
@@ -85,12 +85,6 @@
<p>Cookie processing (etc.) is handled by processor objects, which are an
extension of <code>urllib2</code>'s handlers: <code>HTTPCookieProcessor</code>,
<code>HTTPRefererProcessor</code> etc. They are used like any other handler.
-There is quite a bit of other <code>urllib2</code>-workalike code, too. Note:
-This duplication has gone away in Python 2.4, since 2.4's <code>urllib2</code>
-contains the processor extensions from mechanize, so you can simply use
-mechanize's processor classes direct with 2.4's <code>urllib2</code>; also,
-mechanize's cookie functionality is included in Python 2.4 as module
-<code>cookielib</code> and <code>urllib2.HTTPCookieProcessor</code>.
<p>There is also a <code>urlretrieve()</code> function, which works like
<code>urllib.urlretrieve()</code>.
@@ -136,9 +130,10 @@
you're using <code>mechanize.HTTPCookieProcessor</code> by some other
means), you don't need to call <code>.extract_cookies()</code> or
<code>.add_cookie_header()</code> yourself</strong>. If, on the other hand,
-you don't want to use <code>urllib2</code>, you will need to use this pair of
-methods. You can make your own <code>request</code> and <code>response</code>
-objects, which must support the interfaces described in the docstrings of
+you want to use mechanize to provide cookie handling for an HTTP client other
+than mechanize itself, you will need to use this pair of methods. You can make
+your own <code>request</code> and <code>response</code> objects, which must
+support the interfaces described in the docstrings of
<code>.extract_cookies()</code> and <code>.add_cookie_header()</code>.
<p>There are also some <code>CookieJar</code> subclasses which can store
@@ -319,10 +314,8 @@
out of their site, or out of particular areas of it. This processor uses the
standard Python library's <code>robotparser</code> module. It raises
<code>mechanize.RobotExclusionError</code> (subclass of
-<code>urllib2.HTTPError</code>) if an attempt is made to open a URL prohibited
-by <code>robots.txt</code>. XXX ATM, this makes use of code in the
-<code>robotparser</code> module that uses <code>urllib</code> - this will
-likely change in future to use <code>urllib2</code>.
+<code>mechanize.HTTPError</code>) if an attempt is made to open a URL prohibited
+by <code>robots.txt</code>.
<dt><code>HTTPEquivProcessor</code>
@@ -804,8 +797,6 @@
this?
<p>No: Cookie.py does the server end of the job. It doesn't know when to
accept cookies from a server or when to pass them back.
- <li>Is urllib2.py required?
- <p>No. You probably want it, though.
<li>Where can I find out more about the HTTP cookie protocol?
<p>There is more than one protocol, in fact (see the <a href="./doc.html">docs</a>
for a brief explanation of the history):
@@ -873,18 +864,6 @@
<li>How do I do <X>
<p>The module docstrings are worth reading if you want to do something
unusual.
- <li>What's this "processor" business about? I knew
- <code>urllib2</code> used "handlers", but not these
- "processors".
- <p>This Python library <a href="http://www.python.org/sf/852995">patch</a>
- contains an explanation. Processors are now a standard part of urllib2
- in Python 2.4.
- <li>How do I use it without urllib2.py?
- @{colorize(r"""
-from mechanize import CookieJar
-print CookieJar.extract_cookies.__doc__
-print CookieJar.add_cookie_header.__doc__
-""")}
</ul>
<p>I prefer questions and comments to be sent to the <a
