According to that bug report it is linux only. I did not confirm on Windows, 
but OS X (PySide 1.0.8 Python 2.7.2) has the issue as does Ubuntu (PySide 
1.0.8, I don't recall the python version).

The example code looks like the same issue (non-unicode strings print fine, 
QTextEdit documents (which are unicode) do not). But other than being noted as 
fixed no information. I don't have PySide repo to look up the referenced 
commit, I may have to do that.

Tim Doty

On Dec 5, 2011, at 6:29 AM, paulo alcantara wrote:

> On Sat, Dec 3, 2011 at 5:35 PM, Tim Doty <thoro...@mac.com> wrote:
> 
> On Dec 1, 2011, at 1:58 PM, paulo alcantara wrote:
> > Hi Tim,
> >
> > I tested your code with Python 3 and apiextractor, generatorrunner, 
> > shiboken and pyside all built from
> > the mainline. so I was unable to reproduce this bug, which means I got a 
> > non-empty file. As you know,
> > Python strings are all unicode ones (in Python 3). The minor changes I've 
> > made to your code was to
> > remove the 'u' character in front of the strings[1] and changed all print() 
> > calls to work on Python 3
> > properly.
> 
> Unfortunately it needs to work in Python 2.x. I "updated" to PySide 1.0.9 on 
> OSX Lion and PySide no longer works at all (Qt libraries can't be found, 
> redownloaded and reinstalled to be sure, still doesn't work). That is even 
> worse than 1.0.8 which could at least be imported even if it didn't work 
> right.
> 
> I upgraded to PySide 1.0.4 and PySide now works (QtCore can be located) and 
> QTextStream works with unicode again.
> 
> 
> Hi Tim,
> 
> It seems there must be a regression started from version 1.0.8.
> See http://bugs.pyside.org/show_bug.cgi?id=1063
> 
> 
> 
>                             Paulo
> 
> Tim Doty
> 
> 

_______________________________________________
PySide mailing list
PySide@lists.pyside.org
http://lists.pyside.org/listinfo/pyside

Reply via email to