Message133150
| Author |
lukasz.langa |
| Recipients |
Adam.Groszer, docs@python, lukasz.langa |
| Date |
2011年04月06日.17:43:32 |
| SpamBayes Score |
1.5907975e-05 |
| Marked as misclassified |
No |
| Message-id |
<1302111813.68.0.479273620258.issue11786@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The documentation may be poorly worded but `optionxform()` has always been used also by RawConfigParser. It has been that way since the introduction of this class in Python 2.3 (previously there was only one ConfigParser class which used `optionxform()` since at least Python 1.6).
Both the documentation and the code have seen significant updates in Python 3.2 and there the situation is more explicit.
I'll rephrase the docs for 2.7. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年04月06日 17:43:33 | lukasz.langa | set | recipients:
+ lukasz.langa, docs@python, Adam.Groszer |
| 2011年04月06日 17:43:33 | lukasz.langa | set | messageid: <1302111813.68.0.479273620258.issue11786@psf.upfronthosting.co.za> |
| 2011年04月06日 17:43:32 | lukasz.langa | link | issue11786 messages |
| 2011年04月06日 17:43:32 | lukasz.langa | create |
|