|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
01/May/06 06:50 PM
|
|
With old module importer, where Python*Handler directives are used in a directory context, that directory is added to sys.path. Now where Python code is being used with server side includes in that same directory and code of form:
module = apache.import_module("xxx")
is used with "xxx.py" also being in the same directory, it will be found due to the directory being added to sys.path.
With the new module importer, the directory isn't added to sys.path and so the module would not be found.
In the case of a handler module (rather than SSI Python code), such a module import would still work, as the new module importer is smart enough to realise that the caller was also imported using the new module importer and thus would look in the same directory first or as necessary, in the directory the Python*Handler directive was specified for. This will not work for SSI code though, as it is not part of an imported module and is eval/exec'd on each page request.
What is thus required is for the global environment in which the SSI code is executed for a specific page, to be automatically marked up in such a way that the new module importer believes it was imported as a module by the new module importer, thus triggering it to look in the same directory for modules.
|
|
Description
|
With old module importer, where Python*Handler directives are used in a directory context, that directory is added to sys.path. Now where Python code is being used with server side includes in that same directory and code of form:
module = apache.import_module("xxx")
is used with "xxx.py" also being in the same directory, it will be found due to the directory being added to sys.path.
With the new module importer, the directory isn't added to sys.path and so the module would not be found.
In the case of a handler module (rather than SSI Python code), such a module import would still work, as the new module importer is smart enough to realise that the caller was also imported using the new module importer and thus would look in the same directory first or as necessary, in the directory the Python*Handler directive was specified for. This will not work for SSI code though, as it is not part of an imported module and is eval/exec'd on each page request.
What is thus required is for the global environment in which the SSI code is executed for a specific page, to be automatically marked up in such a way that the new module importer believes it was imported as a module by the new module importer, thus triggering it to look in the same directory for modules.
|
Show » |
made changes - 25/Apr/06 01:04 PM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
In Progress
[ 3
]
|
made changes - 01/May/06 06:50 PM
|
Fix Version/s
|
|
3.3
[ 12310101
]
|
|
Status
|
In Progress
[ 3
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
made changes - 11/Apr/07 11:41 AM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
Sub-task
Closed
Major
