a lot more natural
and trouble-proof, than doubling them and Apache has a lot that could be
used in Zope.
Regards,
Velko Ivanov
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
, when the time
comes to solve this problem.
Regards
Velko Ivanov
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
,
Velko Ivanov
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
as utf8
- put a comment on the first, or second line of the file:
# coding: utf8
this takes care of python's warning
- decode all offending strings:
'some string'.decode('utf8')
Regards,
Velko Ivanov
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub
and I have installed all releases since then, and their
tests are working for me each time.
Regards,
Velko Ivanov
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
much idea what module could be conflicting in the case of
Zope3 and database adapters. The setup is clean, the test machine is
freshly configured and I don't see what could get in the way, but I will
check that more carefully too, if you can not reproduce the error at
your side.
Regards,
Velko
2.4.1 be interfering, as that's
what I'm using ?
Also, is there anybody already working on such tool? It's good to know,
because if yes, I can implement something simple and wait, if not - I'll
implement more generic functionality and interface, so it can be used by
others.
Regards,
Velko Ivanov
is not correct for 3.1.
Removing the __setitem__ def from IMessage solved the problem and the
application is working.
Regards,
Velko Ivanov
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail