|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
mod_python 3.2.0-dev-20050428
|
|
| Resolution Date: |
30/Apr/05 04:31 PM
|
Before the fix for MODPYTHON-9, when you had a module named foobar.py in a published directory, you could access it with a request to /dir/foobar.py, but also with /dir/foobar (the .py was not required since we relied upon the import_module facilities). Now, /dir/foobar is not supported. For compatibility, we should support it and automagically find the proper module.
|
|
Description
|
Before the fix for MODPYTHON-9, when you had a module named foobar.py in a published directory, you could access it with a request to /dir/foobar.py, but also with /dir/foobar (the .py was not required since we relied upon the import_module facilities). Now, /dir/foobar is not supported. For compatibility, we should support it and automagically find the proper module. |
Show » |
made changes - 30/Apr/05 04:31 PM
| Field |
Original Value |
New Value |
|
Resolution
|
|
Fixed
[ 1
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
made changes - 05/Mar/06 01:55 PM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
Bug
Closed
Major
publisher : new module loading mechanism does not allow omiting the '.py' extension
