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 2007/05/16 02:54:16 UTC
[jira] Created: (MODPYTHON-227) PythonOptimize and doc strings.
PythonOptimize and doc strings.
-------------------------------
Key: MODPYTHON-227
URL: https://issues.apache.org/jira/browse/MODPYTHON-227
Project: mod_python
Issue Type: Improvement
Components: core
Affects Versions: 3.3.1
Reporter: Graham Dumpleton
Priority: Minor
When PythonOptimize directive is used and set to "On", the effect is the same as if the options '-O -O' had been supplied to the 'python' executable. Because the highest level of optimisation is enabled, as well as basic optimisations being enabled, any doc strings in modules are discarded. This will cause a problem with any Python modules which make use of doc strings in the way they work. It is suspected for example that this may cause issues with running 'matplotlib'. See:
http://www.modpython.org/pipermail/mod_python/2007-May/023641.html
for further details.
Because someone may want to enable optimisation but not have doc strings be discarded, the PythonOptimize directive should perhaps accept 'Basic' and 'Full' as options instead of just 'On'. For backward compatibility 'On' would equate to 'Full'.
Note that the documentation is also wrong as it says that PythonOptimize is only equivalent to '-O'.
Finally, it doesn't currently matter what you set as the value to PythonOptimize, it always turns the feature on, ie., even if you have:
PythonOptimize Off
The code should check for valid values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MODPYTHON-227) PythonOptimize and doc strings.
Posted by "Toby White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MODPYTHON-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toby White updated MODPYTHON-227:
---------------------------------
Attachment: PythonOptimize.patch
Fix is implemented and documented in attached patch.
> PythonOptimize and doc strings.
> -------------------------------
>
> Key: MODPYTHON-227
> URL: https://issues.apache.org/jira/browse/MODPYTHON-227
> Project: mod_python
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.3.1
> Reporter: Graham Dumpleton
> Priority: Minor
> Attachments: PythonOptimize.patch
>
>
> When PythonOptimize directive is used and set to "On", the effect is the same as if the options '-O -O' had been supplied to the 'python' executable. Because the highest level of optimisation is enabled, as well as basic optimisations being enabled, any doc strings in modules are discarded. This will cause a problem with any Python modules which make use of doc strings in the way they work. It is suspected for example that this may cause issues with running 'matplotlib'. See:
> http://www.modpython.org/pipermail/mod_python/2007-May/023641.html
> for further details.
> Because someone may want to enable optimisation but not have doc strings be discarded, the PythonOptimize directive should perhaps accept 'Basic' and 'Full' as options instead of just 'On'. For backward compatibility 'On' would equate to 'Full'.
> Note that the documentation is also wrong as it says that PythonOptimize is only equivalent to '-O'.
> Finally, it doesn't currently matter what you set as the value to PythonOptimize, it always turns the feature on, ie., even if you have:
> PythonOptimize Off
> The code should check for valid values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MODPYTHON-227) PythonOptimize and doc strings.
Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MODPYTHON-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496169 ]
Graham Dumpleton commented on MODPYTHON-227:
--------------------------------------------
BTW, workaround at present is to set in environment of Apache user the environment variable:
PYTHONOPTIMIZE=1
This will take precedence over the directive due to the order in which things are set.
> PythonOptimize and doc strings.
> -------------------------------
>
> Key: MODPYTHON-227
> URL: https://issues.apache.org/jira/browse/MODPYTHON-227
> Project: mod_python
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.3.1
> Reporter: Graham Dumpleton
> Priority: Minor
>
> When PythonOptimize directive is used and set to "On", the effect is the same as if the options '-O -O' had been supplied to the 'python' executable. Because the highest level of optimisation is enabled, as well as basic optimisations being enabled, any doc strings in modules are discarded. This will cause a problem with any Python modules which make use of doc strings in the way they work. It is suspected for example that this may cause issues with running 'matplotlib'. See:
> http://www.modpython.org/pipermail/mod_python/2007-May/023641.html
> for further details.
> Because someone may want to enable optimisation but not have doc strings be discarded, the PythonOptimize directive should perhaps accept 'Basic' and 'Full' as options instead of just 'On'. For backward compatibility 'On' would equate to 'Full'.
> Note that the documentation is also wrong as it says that PythonOptimize is only equivalent to '-O'.
> Finally, it doesn't currently matter what you set as the value to PythonOptimize, it always turns the feature on, ie., even if you have:
> PythonOptimize Off
> The code should check for valid values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.