Message21787
Logged In: YES
user_id=7733
[anthonybaxter]
> RCP isn't in __all__,
Perhaps it should be, because:
> and isn't documented,
Actually, it is documented:
http://www.python.org/dev/doc/devel/lib/RawConfigParser-objects.html
> we can also put a type check in the
> output code to make sure it gets picked up there...
It gets more and more complicated, doesn't it? I still
think that the code itself wasn't broken so there was no
need to fix it. The simplest solution would be to revert
the rev 1.65 code changes, and just add some documentation.
Something along the lines of: "Output only works with
string values. If used for non-string values, you're on your
own."
We shouldn't be *removing* functionality without a darned
good reason. I don't see such a reason here. And since
this change broke preexisting code that relied on that
functionality, it seems obvious that it should be reverted. |
|
Date |
User |
Action |
Args |
2007-08-23 14:24:13 | admin | link | issue997050 messages |
2007-08-23 14:24:13 | admin | create | |
|