anatoly techtonik <techto...@gmail.com> added the comment: > I suspect this bug will sit here languishing without action, for various > reasons:
I suspect this kind of discussions piss off readers of tickets, but I'll continue, as I do not see any other useful public medium at hand right now. -- start offtopic -- > 1) From other doc discussion, I assume you won’t be able to propose a patch. Right. I do not feel comfortable with Python workflow - now that I have several dozens of unfinished patches - they start to conflict with changes in repository. Conflict resolution takes a lot of time and I can't afford maintaining a separate copy of Python checkout for every patch. It also takes too long to setup test environment and execute tests. There is a lot of yak shaving involved between: 1. make ticket 2. find source 3. make patch 4. test patch 5. attach patch 6. refresh patch 7. test patch 8. attach patch ... I've already explained it somewhere in more detail. A pity it is lost. I am waiting for Mercurial 1.6 to try anchored MQ. Perhaps then I will be able to revisit Python contribution process. > 2) There is no dedicated maintainer for http or cgi. I can not be. pydotorg tools suxx tremendously and I do not feel inspired by wasting time trying to fish required information. To be a maintainer I need: 1. separate commit notifications for the module with ability to reply to dedicated review group 2. separate bug tracker category for my module with giving users ability to change every property of it 3. bug tracker timeline for the module that includes ticket changes, wiki edits, commits and everything else. Filtered. 4. roadmap page with Google Wave content for collaborations 5. dashboard page with links to all the above Look at Trac Hacks for a minimum acceptable example of a tool that is able to persuade me to become a stdlib module developer. Sorry for not able to compile this into a report for EuroPython. > 3) CGI is a low-level, archaic, inefficient interface. stdlib doesn't propose anything better. -- end offtopic -- > 4) The cgi server has grave bugs like this one (from the doc): > “CGI scripts run by the CGIHTTPRequestHandler class cannot execute redirects > (HTTP code 302), because code 200 (script output follows) is sent prior to > execution of the CGI script.” It would be nice if this also clarify if it is the bug of Python class or a limitation of CGI protocol. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9008> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
