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 "Nicolas Lehuen (JIRA)" <ji...@apache.org> on 2005/04/30 09:04:05 UTC

[jira] Created: (MODPYTHON-49) publisher : new module loading mechanism does not allow omiting the '.py' extension

publisher : new module loading mechanism does not allow omiting the '.py' extension
-----------------------------------------------------------------------------------

         Key: MODPYTHON-49
         URL: http://issues.apache.org/jira/browse/MODPYTHON-49
     Project: mod_python
        Type: Bug
 Environment: mod_python 3.2.0-dev-20050428
    Reporter: Nicolas Lehuen
 Assigned to: Nicolas Lehuen 
     Fix For: 3.2.0


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.

-- 
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


[jira] Closed: (MODPYTHON-49) publisher : new module loading mechanism does not allow omiting the '.py' extension

Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/MODPYTHON-49?page=all ]
     
Graham Dumpleton closed MODPYTHON-49:
-------------------------------------


> publisher : new module loading mechanism does not allow omiting the '.py' extension
> -----------------------------------------------------------------------------------
>
>          Key: MODPYTHON-49
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-49
>      Project: mod_python
>         Type: Bug
>  Environment: mod_python 3.2.0-dev-20050428
>     Reporter: Nicolas Lehuen
>     Assignee: Nicolas Lehuen
>      Fix For: 3.2.7

>
> 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.

-- 
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


[jira] Resolved: (MODPYTHON-49) publisher : new module loading mechanism does not allow omiting the '.py' extension

Posted by "Nicolas Lehuen (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/MODPYTHON-49?page=all ]
     
Nicolas Lehuen resolved MODPYTHON-49:
-------------------------------------

    Resolution: Fixed

Fixed - but the mapping rules between an URL and ther resulting module and published object begin to be fairly complicated and conflict-prone...

> publisher : new module loading mechanism does not allow omiting the '.py' extension
> -----------------------------------------------------------------------------------
>
>          Key: MODPYTHON-49
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-49
>      Project: mod_python
>         Type: Bug
>  Environment: mod_python 3.2.0-dev-20050428
>     Reporter: Nicolas Lehuen
>     Assignee: Nicolas Lehuen
>      Fix For: 3.2.0

>
> 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.

-- 
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