You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by "Graham Dumpleton (JIRA)" <ji...@apache.org> on 2006/10/02 05:22:20 UTC

[jira] Work started: (MODPYTHON-187) Hang on subscripted access to request.subprocess_env.

     [ http://issues.apache.org/jira/browse/MODPYTHON-187?page=all ]

Work on MODPYTHON-187 started by Graham Dumpleton.

> Hang on subscripted access to request.subprocess_env.
> -----------------------------------------------------
>
>                 Key: MODPYTHON-187
>                 URL: http://issues.apache.org/jira/browse/MODPYTHON-187
>             Project: mod_python
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.2.10
>         Environment: Apache:     2.0.59
> ModPython:  3.2.10
> Python:     2.4
> OS:         Windows Server 2003
>            Reporter: Alan Kennedy
>         Assigned To: Graham Dumpleton
>             Fix For: 3.3
>
>         Attachments: MP187-2006-08-28-jgallacher-1.diff
>
>
> When subscripted access is used to access variable 'SCRIPT_FILENAME' in the request.subprocess_env table/mapping, the code hangs.
> The following snippet illustrates the problem.
> # -=-=-=-=-=-=
> def postreadrequesthandler(request):
>   request.add_common_vars()
>   value = request.subprocess_env['SCRIPT_FILENAME']    # This hangs
> # value = request.subprocess_env.get('SCRIPT_FILENAME')# This works
>   return apache.OK
> # -=-=-=-=-=-=
> The strange thing is that the .get() access works fine: only the subscript hangs?
> If anyone is wondering about a use-case, I don't actually have one. I was just iterating over the contents of the request.subprocess_env using a for loop (code below), and found that the code hung when accessing 'SCRIPT_FILENAME', and not for any other variable.
> # -=-=-=
> request.add_common_vars()
> d = {}
> for sek in request.subprocess_env.keys():
>   d[sek] = request.subprocess_env[sek]
> # -=-=-=

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira