On 27.06.2012 19:39, Chris McDonough wrote:
On 06/27/2012 12:34 PM, Alexey Luchko wrote:
I've found colander translates error messages of exceptions :) It is
cool and rather surprising, but is not always required.
I'd like to use colander, but translationstring adds one extra
dependency, that is useless for me. Please, could you remove colander
dependency on translationstring in future releases?
No, sorry. I'd just rather not think about the implications of doing this
for the non-universal benefit of one less dependency.
Sorry, I haven't meant to remove use of translationstring from the
colander. Just adding conditional import instead of strict requirement. A
change like the following one does not seem intrusive.
translationstring import could be rewritten like """
try:
import translationstring
except ImportError:
_ = lamba x: x
else:
_ = translationstring.TranslationStringFactory('colander')
""",
isn't it?
Colander is good enough to be used alone, without plone. However, it has
non-universal dependency on translationstring.
--
Regards,
Alex
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
