When I'm using the python webserver I got the 
following message for every access by my client. 
Soryy, I have no experience in Python, so I cannot 
help. This is only a report. 
  
HTTPdaemon_v1.0.0 listening on port 8001 
---------------------------------------- 
Exception happened during processing of request from 
('192.168.1.9', 33917) 
Traceback (most recent call last): 
  File "/home/jb/bin/lib/python2.5/SocketServer.py", 
line 463, in  
process_request_thread 
    self.finish_request(request, client_address) 
  File "/home/jb/bin/lib/python2.5/SocketServer.py", 
line 254, in  
finish_request 
    self.RequestHandlerClass(request, client_address, 
self) 
  File "/home/jb/bin/lib/python2.5/SocketServer.py", 
line 521, in __init__ 
    self.handle() 
  File 
"/home/jb/bin/lib/python2.5/BaseHTTPServer.py", line 
316, in handle 
    self.handle_one_request() 
  File 
"/home/jb/bin/lib/python2.5/BaseHTTPServer.py", line 
310, in  
handle_one_request 
    method() 
  File 
"./src/Myghty-1.0/lib/myghty/http/HTTPServerHandler.py", 
line 53, in  
do_GET 
    self.handle_request() 
  File 
"./src/Myghty-1.0/lib/myghty/http/HTTPServerHandler.py", 
line 56, in  
handle_request 
    httpreq = HSHTTPRequest(self) 
  File 
"./src/Myghty-1.0/lib/myghty/http/HTTPServerHandler.py", 
line 254, in  
__init__ 
    keep_blank_values = True 
  File "/home/jb/bin/lib/python2.5/cgi.py", line 462, 
in __init__ 
    fp = StringIO(qs) 
TypeError: expected read buffer, NoneType found 
---------------------------------------- 
---------------------------------------- 
Exception happened during processing of request from 
('192.168.1.9', 33918) 
Traceback (most recent call last): 
  File "/home/jb/bin/lib/python2.5/SocketServer.py", 
line 463, in  
process_request_thread 
    self.finish_request(request, client_address) 
  File "/home/jb/bin/lib/python2.5/SocketServer.py", 
line 254, in  
finish_request 
    self.RequestHandlerClass(request, client_address, 
self) 
  File "/home/jb/bin/lib/python2.5/SocketServer.py", 
line 521, in __init__ 
    self.handle() 
  File 
"/home/jb/bin/lib/python2.5/BaseHTTPServer.py", line 
316, in handle 
    self.handle_one_request() 
  File 
"/home/jb/bin/lib/python2.5/BaseHTTPServer.py", line 
310, in  
handle_one_request 
    method() 
  File 
"./src/Myghty-1.0/lib/myghty/http/HTTPServerHandler.py", 
line 53, in  
do_GET 
    self.handle_request() 
  File 
"./src/Myghty-1.0/lib/myghty/http/HTTPServerHandler.py", 
line 56, in  
handle_request 
    httpreq = HSHTTPRequest(self) 
  File 
"./src/Myghty-1.0/lib/myghty/http/HTTPServerHandler.py", 
line 254, in  
__init__ 
    keep_blank_values = True 
  File "/home/jb/bin/lib/python2.5/cgi.py", line 462, 
in __init__ 
    fp = StringIO(qs) 
TypeError: expected read buffer, NoneType found 
---------------------------------------- 

Logged In: YES 
user_id=340931

Thanks for the report. Can I ask how you came to use the
as-yet-unreleased Python 2.5 if you have no experience with
Python? It looks like you are having this problem with
Myghty. Does that require Python 2.5? 

FWIW, this looks to me like a problem with Myghty's use of
the cgi module, not a problem with Python itself.

Logged In: YES 
user_id=764593

I suspect that changing 

>>> fp = StringIO(qs)

to 

>>> fp = StringIO(qs or "")

would fix the problem.

If so, this is arguably a bug in myghty.  qs was already 
set to "" unless sys.argv[1] or environ['QUERY_STRING']had 
a value.  Neither of these should ever be None.  (They 
should be either a string, or not found.)

Logged In: YES 
user_id=1558389

> Can I ask how you came to use the 
> as-yet-unreleased Python 2.5 if 
> you have no experience with Python? 
 
We are using Myghty as a webserver, but we have the 
problem python 2.4 eats up all the memory of the small 
embedded system. So I tried with python 2.5 with the new 
memory management...and was stuck at this message. 
I reported this message to improve 2.5 development. Sorry 
if this was a wrong way to do it. 

Logged In: YES 
user_id=764593

This was a fine place to report it; the question is how to 
resolve it now that it is reported.  The catch is that 
cgi.py doesn't seem to have changed, and we're not sure it 
should.