summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2001-11-08 17:19:29 (GMT)
committerFred Drake <fdrake@acm.org>2001-11-08 17:19:29 (GMT)
commitd5214b04f5cc49594a310df75ba8af6dd689ea24 (patch)
treeeba0b1e60f09c7d5814e7cfc166e3bff2cad0406
parent4962fc8fed9697bfbd2218fcd22668e4721495ef (diff)
downloadcpython-d5214b04f5cc49594a310df75ba8af6dd689ea24.zip
cpython-d5214b04f5cc49594a310df75ba8af6dd689ea24.tar.gz
cpython-d5214b04f5cc49594a310df75ba8af6dd689ea24.tar.bz2
Clean up one comment, fix typos in others.
-rw-r--r--Lib/urllib2.py14
1 files changed, 7 insertions, 7 deletions
diff --git a/Lib/urllib2.py b/Lib/urllib2.py
index a1866c6..3f01554 100644
--- a/Lib/urllib2.py
+++ b/Lib/urllib2.py
@@ -72,11 +72,11 @@ f = urllib2.urlopen('http://www.python.org/')
# XXX issues:
# If an authentication error handler that tries to perform
- # authentication for some reason but fails, how should the error be
- # signalled? The client needs to know the HTTP error code. But if
- # the handler knows that the problem was, e.g., that it didn't know
- # that hash algo that requested in the challenge, it would be good to
- # pass that information along to the client, too.
+# authentication for some reason but fails, how should the error be
+# signalled? The client needs to know the HTTP error code. But if
+# the handler knows that the problem was, e.g., that it didn't know
+# that hash algo that requested in the challenge, it would be good to
+# pass that information along to the client, too.
# XXX to do:
# name!
@@ -328,8 +328,8 @@ class OpenerDirector:
def error(self, proto, *args):
if proto in ['http', 'https']:
- # XXX http[s] protocols are special cased
- dict = self.handle_error['http'] # https is not different then http
+ # XXX http[s] protocols are special-cased
+ dict = self.handle_error['http'] # https is not different than http
proto = args[2] # YUCK!
meth_name = 'http_error_%d' % proto
http_err = 1