durusmail: durus-users: Durus: my experience and trouble [SOLVED]
Durus: my experience and trouble
2005-10-25
2005-10-25
2005-10-25
2005-10-25
2005-10-25
Durus: my experience and trouble [SOLVED]
2005-10-26
Durus: my experience and trouble [SOLVED]
Kai Schmidt
2005-10-26
Hi David, hi all,

my problem with Durus is solved! Thanks David and others. And it was "my
[setup]" problem. In my bigger QT, pyqt program, there was one qt.QString
Object stored in Durus, making the trouble, coming from some Listbox-input.
PyQT does transparent conversion between Stringtypes (and there are many,
including encoding like utf8) and you tend to forget those differences. I now
feed only explicit str() or unicode() [with utf8 encoding] to Durus, and can
now read and store without that ugly memory error.
I suspected my German Umlauts to be the bad guy, but this is at least cought
by a key_error exception if you use two apparently identical (looking)
strings as OIDs in Durus. One of those is UTF-8 encoded, where it is not
possible to predict the content-related memory-size, of that string. QT also
delivers C-type strings (zero-terminated). That smelled like pointer errors
with UTF8.

Anyway I will be more carefull what to put into Durus ;=)

Thanks again and see you around

Kai

reply