On Wed, 1 Nov 2000, Phil Thompson wrote:
> This is sensible, but can't be achieved. It is Python raising the
> exception (not PyQt) because PyQt is returning the None object instead
> of a string object. PyQt could return a string object containing "None"
> (although "null" would be better) but then 'print QString()' and 'print
> QString("None")' would do exactly the same thing.
>
I found that out, too, after a bit of hacking around. I think it might
be best to keep the current behavious, but document it explicitly.
Shall I write a paragraph or two for in the PyQt documentation?
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
PyKDE mailing list [EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
- [PyKDE] Printing empty QStrings Boudewijn Rempt
- Re: [PyKDE] Printing empty QStrings Phil Thompson
- Re: [PyKDE] Printing empty QStrings Boudewijn Rempt
- Re: [PyKDE] Printing empty QStrings Phil Thompson
- Re: [PyKDE] Printing empty QStrings Boudewijn Rempt
- Re: [PyKDE] Printing empty QStrings Johannes Sixt
- Re: [PyKDE] Printing empty QStrings Andrew Kuchling
- Re: [PyKDE] Printing empty QStrings Phil Thompson
- Re: [PyKDE] Printing empty QStrings Phil Thompson
- Re: [PyKDE] Printing empty QStrings Pete Ware
- Re: [PyKDE] Printing empty QStrings Phil Thompson
- Re: [PyKDE] Printing empty QStrings Andrew Kuchling
- Re: [PyKDE] Printing empty QStrings Phil Thompson
- Re: [PyKDE] Printing empty QStrings Coy Krill
- Re: [PyKDE] Printing empty QStrings Phil Thompson
