[issue7133] test_ssl failure

2011-09-22 Thread Keith Briggs 

Keith Briggs  added the comment:

I am still getting this error with SocketServer in Python 2.7.2, even though it 
looks the same as was fixed in Issue7133:

  File "/usr/local/lib/python2.7/SocketServer.py", line 284, in 
_handle_request_noblock
self.process_request(request, client_address)
  File "/usr/local/lib/python2.7/SocketServer.py", line 310, in process_request
self.finish_request(request, client_address)
  File "/usr/local/lib/python2.7/SocketServer.py", line 323, in finish_request
self.RequestHandlerClass(request, client_address, self)
  File "/usr/local/lib/python2.7/SocketServer.py", line 641, in __init__
self.finish()
  File "/usr/local/lib/python2.7/SocketServer.py", line 694, in finish
self.wfile.flush()
  File "/usr/local/lib/python2.7/socket.py", line 303, in flush
self._sock.sendall(view[write_offset:write_offset+buffer_size])
TypeError: must be string or read-only buffer, not memoryview


Keith

--
nosy: +kbriggs

___
Python tracker 
<http://bugs.python.org/issue7133>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7133] test_ssl failure

2011-09-26 Thread Keith Briggs 

Keith Briggs  added the comment:

Senthil: thanks for the reply.   That's how I did build python 2.7.2 anyway.   
But I can't see anything about SSL in the generated config files.However, 
on another system (Fedora 15 with python 2.7.1), I don't get the problem.
In case it's useful, I was trying to run the recipe 
http://code.activestate.com/recipes/573444-threaded-documenting-xml-rpc-server-over-https/?c=13559
 when this crash happened.   Is there something in that recipe which is not 
compatible with the current python modules?  

Keith

--

___
Python tracker 
<http://bugs.python.org/issue7133>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4278] optparse quirks

2008-11-07 Thread Keith Briggs 

New submission from Keith Briggs <[EMAIL PROTECTED]>:

I got the message:

optparse.OptionError: invalid long option string '-T0': must start with
--, followed by non-dash

This is bad - the real error was that I gave a short option which did
not have a single letter.

Also, it seems that add_option('--height-of-plot','-h') is not allowed,
because -h can only go with --help.   How do I override this?

Keith

--
components: Extension Modules
messages: 75602
nosy: kbriggs
severity: normal
status: open
title: optparse quirks
type: behavior
versions: Python 2.5.3

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4278>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4869] random.expovariate(0.0)

2009-01-07 Thread Keith Briggs 

New submission from Keith Briggs :

random.expovariate(lambd) should handle lambd=0 cleanly, and probably
return a FP infinity.

At the moment it gives:

ZeroDivisionError: float division

--
components: Extension Modules
messages: 79346
nosy: kbriggs
severity: normal
status: open
title: random.expovariate(0.0)
versions: Python 2.6

___
Python tracker 
<http://bugs.python.org/issue4869>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4869] random.expovariate(0.0)

2009-01-07 Thread Keith Briggs 

Keith Briggs  added the comment:

That's all true - the only thing in favour of my suggestion is that to
allow lambda=0 is sometimes useful in simulations, meaning that it's
infinite time to the next event, i.e. it never occurs.  A FP infinity
would do this without requiring a special case.

At least the documentation should state the restrictions on lambda.

___
Python tracker 
<http://bugs.python.org/issue4869>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com