[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2012-07-08 Thread Éric Araujo
Éric Araujo added the comment: You need to indent the block after the versionchanged directive. Also, I believe only bug fixes should go into 3.3 now that we are in beta. -- nosy: +eric.araujo ___ Python tracker

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2012-07-07 Thread Senthil Kumaran
Changes by Senthil Kumaran : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 3.3 -Python 3.4 ___ Python tracker ___ ___

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2012-07-07 Thread Phillip J. Eby
Phillip J. Eby added the comment: On Sat, Jul 7, 2012 at 2:37 PM, Terry J. Reedy wrote: > Phillip, this is a trivial wsgiref patch. Do you have any opinion? > Nope. -- ___ Python tracker _

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2012-07-07 Thread Senthil Kumaran
Senthil Kumaran added the comment: I have fixed this in the changeset 34e705fa4da4. SERVER_SOFTWARE term can be made more specific to note the implementation as various suggestions say. I personally think, it is worthy to make change in 3.3 itself as its been open from a long time and it is s

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2012-07-07 Thread Terry J. Reedy
Terry J. Reedy added the comment: Phillip, this is a trivial wsgiref patch. Do you have any opinion? -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ _

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2012-07-07 Thread Greg Roodt
Greg Roodt added the comment: Bumping as part of bug scrub at EuroPython. Patch seems sensible to me. Obvious options to me are to either accept patch, close bug or write docs. Bug has not seen activity in years, so can probably be closed. -- nosy: +groodt ___

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2010-08-03 Thread David Stanek
Changes by David Stanek : -- nosy: +dstanek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2010-08-03 Thread Terry J. Reedy
Terry J. Reedy added the comment: In the absence of doc claiming the requested behavior, this is a feature request. In principle, it seems sensible, but I do not use the module. Support from more than one person, perhaps from python-list or web-sig list (not sure of name) would be good. Asid

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2009-09-27 Thread Thijs Triemstra
Thijs Triemstra added the comment: Here's a patch that uses platform.python_implementation instead, producing: >>> from wsgiref import simple_server >>> simple_server.software_version 'WSGIServer/0.1 CPython/2.7a0' >>> This will become relevant when Jython and IronPython start using these m

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2009-05-04 Thread Benjamin Peterson
Changes by Benjamin Peterson : -- assignee: -> pje nosy: +pje ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue5931] Python runtime name hardcoded in wsgiref.simple_server

2009-05-04 Thread Thijs Triemstra
New submission from Thijs Triemstra : While testing the following script on Jython 2.5b4 I noticed it returned SERVER_SOFTWARE = 'WSGIServer/0.1 Python/2.5b4+' instead of the expected 'WSGIServer/0.1 Jython/2.5b4+'. This is because the word 'Python' is hardcoded in simple_server.py; "sys_versi