From david.garcia at upf.edu  Mon Sep  3 03:48:17 2012
From: david.garcia at upf.edu (=?ISO-8859-1?Q?David_Garc=EDa_Garz=F3n?=)
Date: Mon, 03 Sep 2012 03:48:17 +0200
Subject: [PySide] Obtaining QObject from PySide based PyObject (complete)
In-Reply-To: <10684831.0hduZLiNck@hugodesktop>
References: <96152238.d566e79Gsm@wl082936> <10046387.5KaC9rtBQY@hugodesktop>
	<1564282.WylHtcGgKK@wl082936> <10684831.0hduZLiNck@hugodesktop>
Message-ID: <50440C61.3050302@upf.edu>

On 28/08/12 16:25, Hugo Parente Lima wrote:
> On Tuesday, August 28, 2012 02:48:32 PM David García Garzón wrote:
>> On Monday 27 August 2012 16:23:03 Hugo Parente Lima wrote:
>>> On Monday, August 27, 2012 09:12:27 PM David García Garzón wrote:
>>>> Sorry for the previous unfinished message. Here goes the final one.
>>>>
>>>> I am porting a CPython library (boost based indeed) from PyQt to PySide.
>>>> I had a function in the library that received a Sip wrapped widget
>>>> as a PyObject and I used the very ugly SIP api to recover a pointer to
>>>> the
>>>> actual C++ QObject.
>>>>
>>>> Does anyone know how recover the C++ QObject from the PyObject in
>>>> PySide?
>>> You can use:
>>> Shiboken::Object::cppPointer(...), it's on libshiboken basewrapper.h
>>>
>>> It receives two parameters, a SbkObject* and a PyTypeObject*, the
>>> SbkObject* will be your PyObject*, just cast it and make sure it always
>>> will be a Python object representing a C++ object bound using Shiboken,
>>> the
>>> PyTypeObject* must be the PyTypeObject* for QObject, you can get it using:
>>>
>>> Shiboken::TypeResolver::get("QObject*")->pythonType();
>>>
>>> TypeResolver class is located on libshiboken typeresolver.h header.
>>>
>>> Hope this would help you.
>> Yes, thanks, this seems to be just what i needed. You even provided answer
>> to what i wanted to ask next, how to identify pyside objects. No time to
>> try it just now but i am eager to try it to see if it works. Thanks a lot.
> There's a function on basewrapper.h that do just that, test if the PyObject is
> a SbkObject, i.e. a PySide object.
>
> Shiboken::Object::checkType(PyObject*)
>
> Returns true if the object is an instance of a type created by the Shiboken
> generator.
>

Thanks for all the help. Here it is the final working code, so people 
following this thread in the future can take it:

void * shibokenUnwrap(PyObject * pyobject)
{
	if (not Shiboken::Object::checkType(pyobject))
		return error("Not a shiboken object");

	SbkObject * sbkobject = (SbkObject *) pyobject;

	PyTypeObject * type = Shiboken::SbkType<QObject>();

	void * cppobject = Shiboken::Object::cppPointer(sbkobject, type);
	if (not cppobject)
		return error("Not a QObject");

	return cppobject;
}


Notice, that I had to change the proposed line to get the type because 
it crashed:
	PyTypeObject* type =
		Shiboken::TypeResolver::get("QObject*")->pythonType();
instead, i wrote:
	PyTypeObject * type = Shiboken::SbkType<QObject>();


I also found a high level function to do the wrapping:

PyObject * shibokenWrap(QObject * qobject)
{
	return Shiboken::createWrapper(qobject, /*python owns*/ false);
}


Let me launch one more question: Now, besides imports, i almost have the 
same user code for PyQt[1] and PySide[2]... but a function 
loadUi(uifile) which has to choose which wrapper to use to return the 
loaded widget to python. I had to provide a different 
loadUiPySide(uifile) which wraps using shiboken instead.

But i would like a user code transparent solution, so, is there any way 
to know which of the two frameworks is being used? from c++ (better), 
from the python library (also good) but not from the user python code.


David.

[1] http://clam-project.org/clam/trunk/ipyclam/demo_ipyclam_pyqt_sms
[2] http://clam-project.org/clam/trunk/ipyclam/demo_ipyclam_pyside_sms




From Zhu.Zhong at alcatel-sbell.com.cn  Mon Sep  3 10:44:49 2012
From: Zhu.Zhong at alcatel-sbell.com.cn (ZHONG Zhu)
Date: Mon, 3 Sep 2012 08:44:49 +0000
Subject: [PySide] [Shiboken] Can't generate
Message-ID: <E2C879D9F3A55B44BF5818CEE6D385D91264AA@CNSHJMBX02.ad4.ad.alcatel.com>

Hi All,

I'm trying to follow the Shiboken tutorial at http://qt-project.org/wiki/Category:LanguageBindings::PySide::Shiboken::PySide_Binding_Generation_Tutorial to build the foo project on Windows XP. My understanding is that after I called
"
generatorrunner --generatorSet=shiboken global.h --include-paths="D:\workspace\Shiboken\binding-tutorial\libfoo;D:\Qt\4.8.1\include\Qt;D:/Qt/4.8.1/include/QtCore;D:/Qt/4.8.1/include/QtGui;D:\workspace\Shiboken\pyside-pyside-archive\PySide\QtCore"  --typesystem-paths=".;D:/workspace/Shiboken/pyside-pyside-archive/PySide;D:/workspace/Shiboken/pyside-pyside-archive/PySide/QtCore" --output-directory=. typesystem_foo.xml
"
I should have 4 files like below
foo/foo_python.h
foo/foo_module_wrapper.cpp
foo/math_wrapper.h
foo/math_wrapper.cpp

but actually, only 2 files got generated. Anyone has any idea? Thanks in advance!
foo/foo_python.h
foo/foo_module_wrapper.cpp

BR,

Zhu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120903/b42ab501/attachment.html>

From yann.lanthony at gmail.com  Mon Sep  3 11:24:04 2012
From: yann.lanthony at gmail.com (Yann Lanthony)
Date: Mon, 3 Sep 2012 11:24:04 +0200
Subject: [PySide] [Shiboken] Can't generate
In-Reply-To: <E2C879D9F3A55B44BF5818CEE6D385D91264AA@CNSHJMBX02.ad4.ad.alcatel.com>
References: <E2C879D9F3A55B44BF5818CEE6D385D91264AA@CNSHJMBX02.ad4.ad.alcatel.com>
Message-ID: <CAMS3xu=2HnuwwsZg+z7BgsMxNy7LZ+HR6EyD5ykL041U_wkAag@mail.gmail.com>

Hi,

If you don't have those files, it generally means that Shiboken couldn't
find the definition of your Math class.
You probably have some errors or warnings when launching your command line,
it could be useful to report them.
If you have something like "class 'Math' is specified in typesystem but not
defined", make sure that the header of your original Math class is in the
include path and that your global.h includes it.

Also, you will find in the output directory some log files that can help
you understand why Shiboken fails generating a wrapper for your call.
Don't hesitate to send a zipped version of your project if you can't make
it work.

Regards,
Yann

2012/9/3 ZHONG Zhu <Zhu.Zhong at alcatel-sbell.com.cn>

>  Hi All,
>
> I’m trying to follow the Shiboken tutorial at *
> http://qt-project.org/wiki/Category:LanguageBindings::PySide::Shiboken::PySide_Binding_Generation_Tutorial
> *<http://qt-project.org/wiki/Category:LanguageBindings::PySide::Shiboken::PySide_Binding_Generation_Tutorial>to build the foo project on Windows XP. My understanding is that after I
> called
> “
> generatorrunner --generatorSet=shiboken global.h
> --include-paths="D:\workspace\Shiboken\binding-tutorial\libfoo;D:\Qt\4.8.1\include\Qt;D:/Qt/4.8.1/include/QtCore;D:/Qt/4.8.1/include/QtGui;D:\workspace\Shiboken\pyside-pyside-archive\PySide\QtCore"
> --typesystem-paths=".;D:/workspace/Shiboken/pyside-pyside-archive/PySide;D:/workspace/Shiboken/pyside-pyside-archive/PySide/QtCore"
> --output-directory=. typesystem_foo.xml
> “
> I should have 4 files like below
> foo/foo_python.h
> foo/foo_module_wrapper.cpp
> foo/math_wrapper.h
> foo/math_wrapper.cpp
>
> but actually, only 2 files got generated. Anyone has any idea? Thanks in
> advance!
> foo/foo_python.h
> foo/foo_module_wrapper.cpp
>
> BR,
>
> Zhu
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120903/fa2a1c6b/attachment.html>

From david.garcia at upf.edu  Mon Sep  3 17:47:47 2012
From: david.garcia at upf.edu (David =?ISO-8859-1?Q?Garc=EDa_Garz=F3n?=)
Date: Mon, 03 Sep 2012 17:47:47 +0200
Subject: [PySide] Detecting which framework (PyQt or PySide) is active
Message-ID: <1980128.uz9bEzbLH5@wl082936>

Hi, i am working on a CPython function i want to transparently run with either 
PyQt or PySide. It is a functions that builds an interface using C++ and then 
wraps it using either Sip (PyQt) or shiboken (PySide) in order to return it to 
python. The wrapping part was solved thanks to your help in a different thread 
but i still have the problem of knowing which wrapper i should use in a given 
situation.

Is there some state (function, singletons, globals...) i could check? I am 
thinking on the pyside created QApp or any PySide state it requires to be 
initializated.

Additional info: The library is split in two layers, a python and a C one, so 
it could be either api, but not in user code, so solution such as checking the 
imported modules are not convinient. If there is no api for that i am thinking 
in hacks like using PySide initializations required by QApp if any.

Any ideas?

David.



From a.richi at bluewin.ch  Mon Sep  3 18:16:09 2012
From: a.richi at bluewin.ch (Aaron Richiger)
Date: Mon, 03 Sep 2012 18:16:09 +0200
Subject: [PySide] Detecting which framework (PyQt or PySide) is active
In-Reply-To: <1980128.uz9bEzbLH5@wl082936>
References: <1980128.uz9bEzbLH5@wl082936>
Message-ID: <5044D7C9.8020506@bluewin.ch>

Hello David!

As far as I know, there is no direct function in the PySide (Qt) API to 
get the used technology. But others may know more... I could imagine two 
solutions:
- Dirty hack: Some things work in PySide, that do not work with PyQt4. 
You could try one of them and if it fails, then know that you are on PyQt4
- Get the info from the built-ins of the QApplication.instance() object, 
e.g. __repr__ . I wrote the following little script that checks what you 
asked for, but don't know whether it's usable for your purpose:


############ Code ####################
import sys

from PySide.QtCore import *
from PySide.QtGui import *

# from PyQt4.QtCore import *
# from PyQt4.QtGui import *

def is_PySide():
     return 'PySide' in repr(QApplication.instance())

def is_PyQt4():
     return 'PyQt4' in repr(QApplication.instance())


if __name__ == '__main__':
     app = QApplication(sys.argv)
     w = QWidget()
     w.show()
     print 'Is PySide:', is_PySide()
     print 'Is PyQt4: ', is_PyQt4()
     sys.exit(app.exec_())

###################################



Am 03.09.2012 17:47, schrieb David García Garzón:
> Hi, i am working on a CPython function i want to transparently run with either
> PyQt or PySide. It is a functions that builds an interface using C++ and then
> wraps it using either Sip (PyQt) or shiboken (PySide) in order to return it to
> python. The wrapping part was solved thanks to your help in a different thread
> but i still have the problem of knowing which wrapper i should use in a given
> situation.
>
> Is there some state (function, singletons, globals...) i could check? I am
> thinking on the pyside created QApp or any PySide state it requires to be
> initializated.
>
> Additional info: The library is split in two layers, a python and a C one, so
> it could be either api, but not in user code, so solution such as checking the
> imported modules are not convinient. If there is no api for that i am thinking
> in hacks like using PySide initializations required by QApp if any.
>
> Any ideas?
>
> David.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside



From david.garcia at upf.edu  Mon Sep  3 19:28:12 2012
From: david.garcia at upf.edu (David =?ISO-8859-1?Q?Garc=EDa_Garz=F3n?=)
Date: Mon, 03 Sep 2012 19:28:12 +0200
Subject: [PySide] Detecting which framework (PyQt or PySide) is active
In-Reply-To: <5044D7C9.8020506@bluewin.ch>
References: <1980128.uz9bEzbLH5@wl082936> <5044D7C9.8020506@bluewin.ch>
Message-ID: <1948702.PKeuZHMWBT@wl082936>

That wont work in my case. To clarify the situation with some simplified code:
#################################
# This is user code.
# User could either choose PyQt4 or PySide
#from PyQt4 import QtGui
from PySide import QtGui
import mylib  # that's the lib i am coding

# my guess: this will trigger framework dependant initializations
app = QApplication(sys.argv)
w = mylib.createInterface()
w.show()
app.exec_()

##############################
# This is the python layer of mylib
# imports from previous file are not available
# Indeed we could need to import both
import PyQt4.QtGui
import PySide.QtGui

def createInterface() :
	if isPySideInitialized() : # Required functionality!!
		return createInterfacePySide()
	else :
		return createInterfacePyQt4()

///////////////////////////////////////////////
// This is C++ layer of mylib
QWidget * createInterface(...)
{
	return new QPushButton();
}
PyObject * createInterfacePyQt4(...)
{
	return SipWrap(createInterface());
}
PyObject * createInterfacePySide(..)
{
	return ShibokenWrap(createInterface());
}

The decision could be made delayed to the C++ code if there is any mean from 
C++, but it should be done at library layer, to avoid tainting user code with 
such nasty ehem... details.

Maybe on the line of your dirty hacks, instead of doing something that do not 
work for either framework, we should try something that it won't work (but 
fails safely with an exception) if the framework is not initialized.

David.


On Monday 03 September 2012 18:16:09 Aaron Richiger wrote:
> Hello David!
> 
> As far as I know, there is no direct function in the PySide (Qt) API to
> get the used technology. But others may know more... I could imagine two
> solutions:
> - Dirty hack: Some things work in PySide, that do not work with PyQt4.
> You could try one of them and if it fails, then know that you are on PyQt4
> - Get the info from the built-ins of the QApplication.instance() object,
> e.g. __repr__ . I wrote the following little script that checks what you
> asked for, but don't know whether it's usable for your purpose:
> 
> 
> ############ Code ####################
> import sys
> 
> from PySide.QtCore import *
> from PySide.QtGui import *
> 
> # from PyQt4.QtCore import *
> # from PyQt4.QtGui import *
> 
> def is_PySide():
>      return 'PySide' in repr(QApplication.instance())
> 
> def is_PyQt4():
>      return 'PyQt4' in repr(QApplication.instance())
> 
> 
> if __name__ == '__main__':
>      app = QApplication(sys.argv)
>      w = QWidget()
>      w.show()
>      print 'Is PySide:', is_PySide()
>      print 'Is PyQt4: ', is_PyQt4()
>      sys.exit(app.exec_())
> 
> ###################################
> 
> Am 03.09.2012 17:47, schrieb David García Garzón:
> > Hi, i am working on a CPython function i want to transparently run with
> > either PyQt or PySide. It is a functions that builds an interface using
> > C++ and then wraps it using either Sip (PyQt) or shiboken (PySide) in
> > order to return it to python. The wrapping part was solved thanks to your
> > help in a different thread but i still have the problem of knowing which
> > wrapper i should use in a given situation.
> > 
> > Is there some state (function, singletons, globals...) i could check? I am
> > thinking on the pyside created QApp or any PySide state it requires to be
> > initializated.
> > 
> > Additional info: The library is split in two layers, a python and a C one,
> > so it could be either api, but not in user code, so solution such as
> > checking the imported modules are not convinient. If there is no api for
> > that i am thinking in hacks like using PySide initializations required by
> > QApp if any.
> > 
> > Any ideas?
> > 
> > David.
> > 
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
> 
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From Zhu.Zhong at alcatel-sbell.com.cn  Wed Sep  5 08:54:12 2012
From: Zhu.Zhong at alcatel-sbell.com.cn (ZHONG Zhu)
Date: Wed, 5 Sep 2012 06:54:12 +0000
Subject: [PySide] [Shiboken] Can't generate
In-Reply-To: <CAMS3xu=2HnuwwsZg+z7BgsMxNy7LZ+HR6EyD5ykL041U_wkAag@mail.gmail.com>
References: <E2C879D9F3A55B44BF5818CEE6D385D91264AA@CNSHJMBX02.ad4.ad.alcatel.com>
	<CAMS3xu=2HnuwwsZg+z7BgsMxNy7LZ+HR6EyD5ykL041U_wkAag@mail.gmail.com>
Message-ID: <E2C879D9F3A55B44BF5818CEE6D385D9129AC4@CNSHJMBX02.ad4.ad.alcatel.com>

Hi Yann,

Thank you so much for your quick reply. I tried many ways but still can't make Shiboken find my Math class. No foo/math_wrapper.h & foo/math_wrapper.cpp created. Could you please help to take a look at my project files (in libfoo.zip)?Attached also

-          ShibokenOutPut.txt shows the output of generatorrunner from DOS console, I see many warnings but no error

-          Other .log files generated by generatorrunner

Thanks in advance!

Zhu

From: Yann Lanthony [mailto:yann.lanthony at gmail.com]
Sent: Monday, September 03, 2012 5:24 PM
To: ZHONG Zhu
Cc: pyside at qt-project.org
Subject: Re: [PySide] [Shiboken] Can't generate

Hi,

If you don't have those files, it generally means that Shiboken couldn't find the definition of your Math class.
You probably have some errors or warnings when launching your command line, it could be useful to report them.
If you have something like "class 'Math' is specified in typesystem but not defined", make sure that the header of your original Math class is in the include path and that your global.h includes it.

Also, you will find in the output directory some log files that can help you understand why Shiboken fails generating a wrapper for your call.
Don't hesitate to send a zipped version of your project if you can't make it work.

Regards,
Yann

2012/9/3 ZHONG Zhu <Zhu.Zhong at alcatel-sbell.com.cn<mailto:Zhu.Zhong at alcatel-sbell.com.cn>>
Hi All,

I'm trying to follow the Shiboken tutorial at http://qt-project.org/wiki/Category:LanguageBindings::PySide::Shiboken::PySide_Binding_Generation_Tutorial to build the foo project on Windows XP. My understanding is that after I called
"
generatorrunner --generatorSet=shiboken global.h --include-paths="D:\workspace\Shiboken\binding-tutorial\libfoo;D:\Qt\4.8.1\include\Qt;D:/Qt/4.8.1/include/QtCore;D:/Qt/4.8.1/include/QtGui;D:\workspace\Shiboken\pyside-pyside-archive\PySide\QtCore"  --typesystem-paths=".;D:/workspace/Shiboken/pyside-pyside-archive/PySide;D:/workspace/Shiboken/pyside-pyside-archive/PySide/QtCore" --output-directory=. typesystem_foo.xml
"
I should have 4 files like below
foo/foo_python.h
foo/foo_module_wrapper.cpp
foo/math_wrapper.h
foo/math_wrapper.cpp

but actually, only 2 files got generated. Anyone has any idea? Thanks in advance!
foo/foo_python.h
foo/foo_module_wrapper.cpp

BR,

Zhu


_______________________________________________
PySide mailing list
PySide at qt-project.org<mailto:PySide at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/pyside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libfoo.zip
Type: application/x-zip-compressed
Size: 11162 bytes
Desc: libfoo.zip
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ShibokenOutPut.txt
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjb_rejected_enums.log
Type: application/octet-stream
Size: 1056 bytes
Desc: mjb_rejected_enums.log
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjb_rejected_fields.log
Type: application/octet-stream
Size: 1075 bytes
Desc: mjb_rejected_fields.log
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjb_rejected_functions.log
Type: application/octet-stream
Size: 1243 bytes
Desc: mjb_rejected_functions.log
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjb_rejected_classes.log
Type: application/octet-stream
Size: 1115 bytes
Desc: mjb_rejected_classes.log
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/81f15178/attachment-0003.obj>

From c.l.l.bartels at gmail.com  Wed Sep  5 09:32:38 2012
From: c.l.l.bartels at gmail.com (Chris Bartels)
Date: Wed, 5 Sep 2012 09:32:38 +0200
Subject: [PySide] windows builds pyside + qt 4.8
Message-ID: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>

Hi all,

Is there anyone who has succesfully build PySide Windows binaries with
qt 4.8? (If so, are they willing to share them?) I desperately need
the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
haven't been able to build PySide.)

Chris


From backup.rlacko at gmail.com  Wed Sep  5 09:45:23 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 5 Sep 2012 09:45:23 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
Message-ID: <CAHC6v6i4dNLT1ftUqakXP9z68OVnyTCXR-wfwu-vbH3V_ydUWg@mail.gmail.com>

Hi,

2012/9/5 Chris Bartels <c.l.l.bartels at gmail.com>:
> Hi all,
>
> Is there anyone who has succesfully build PySide Windows binaries with
> qt 4.8? (If so, are they willing to share them?) I desperately need
> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
> haven't been able to build PySide.)
>
> Chris
>
I have some problems with 64bit but 32bit are building without
problems. I will try to create the builds for windows ASAP.

Regards
Roman

_______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From bjelge at nefines.com  Wed Sep  5 09:47:52 2012
From: bjelge at nefines.com (=?ISO-8859-1?Q?Bj=F8rn_Helge_Kj=F8snes?=)
Date: Wed, 05 Sep 2012 09:47:52 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
Message-ID: <504703A8.1030603@nefines.com>

Hi,

I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I 
have not made any packages but I can share my build batch file. I use 
this batch file in a Visual Studio 2008 Command Prompt. You have to have 
a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source 
using Visula Studio 2008 if you want the debug versions as well as the 
release version. I guess you can use the stock versions of but Qt and 
Python if  you just remove the debug build parts of the batch file.


SET QTDIR=\Projects\Qt\QT482\
SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
SET PYTHONVER=27
SET PYSIDESOURCEDIR=\Projects\PySide\
SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
SET QTDIR=E:\Projects\QT\QT482
SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\

SET 
PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%PATH%

@echo make install dir
mkdir %PYSIDEINSTALLDIR%
@echo go to pyside source dir
cd %PYSIDESOURCEDIR%
@echo make install dir
mkdir %PSINSTALLR%

@echo PySide build shiboken release
cd %SHIBOKENDIR%
mkdir buildrelease
cd buildrelease
cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE 
-DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe" 
-DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib 
-DLIBXML2_INCLUDE_DIR=%LIBXML%include 
-DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib 
-DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include 
-DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
nmake install
copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
@echo PySide build shiboken debug
mkdir %PSINSTALLD%
cd %SHIBOKENDIR%
mkdir builddebug
cd builddebug
cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE 
-DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe" 
-DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib" 
-DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib" 
-DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib 
-DLIBXML2_INCLUDE_DIR=%LIBXML%include 
-DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib 
-DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include 
-DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
nmake install
copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin

@echo PySide build pyside release
cd %PYSIDEDIR%
mkdir buildrelease
cd buildrelease
cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE 
-DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
nmake install
@echo PySide build pyside debug
cd %PYSIDEDIR%
mkdir builddebug
cd builddebug
cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE 
-DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
nmake install
@echo PySide build pyside tools release
cd %PYSIDETOOLSDIR%
mkdir buildrelease
cd buildrelease
cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE 
-DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
nmake install

@echo PySide build pyside tools debug
cd %PYSIDETOOLSDIR%
mkdir builddebug
cd builddebug
cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE 
-DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
nmake install

cd %PYSIDEINSTALLDIR%
@echo Done building PySide Debug and Release version


Regards,
Bjørn Helge Kjøsnes

On 05.09.2012 09:32, Chris Bartels wrote:
> Hi all,
>
> Is there anyone who has succesfully build PySide Windows binaries with
> qt 4.8? (If so, are they willing to share them?) I desperately need
> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
> haven't been able to build PySide.)
>
> Chris
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>



From backup.rlacko at gmail.com  Wed Sep  5 09:57:05 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 5 Sep 2012 09:57:05 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <504703A8.1030603@nefines.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
	<504703A8.1030603@nefines.com>
Message-ID: <CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>

Hi Bjorn,

2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
> Hi,
>
> I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I
> have not made any packages but I can share my build batch file. I use
> this batch file in a Visual Studio 2008 Command Prompt. You have to have
> a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source
> using Visula Studio 2008 if you want the debug versions as well as the
> release version. I guess you can use the stock versions of but Qt and
> Python if  you just remove the debug build parts of the batch file.
Please can You send configure.exe parameters used when building Qt from source ?
Thanks

>
>
> SET QTDIR=\Projects\Qt\QT482\
> SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
> SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
> SET PYTHONVER=27
> SET PYSIDESOURCEDIR=\Projects\PySide\
> SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
> SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
> SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
> SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
> SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
> SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
> SET QTDIR=E:\Projects\QT\QT482
> SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
> SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
> SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
> SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\
>
> SET
> PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%PATH%
>
> @echo make install dir
> mkdir %PYSIDEINSTALLDIR%
> @echo go to pyside source dir
> cd %PYSIDESOURCEDIR%
> @echo make install dir
> mkdir %PSINSTALLR%
>
> @echo PySide build shiboken release
> cd %SHIBOKENDIR%
> mkdir buildrelease
> cd buildrelease
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
> -DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe"
> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> nmake install
> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
> @echo PySide build shiboken debug
> mkdir %PSINSTALLD%
> cd %SHIBOKENDIR%
> mkdir builddebug
> cd builddebug
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> -DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe"
> -DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib"
> -DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib"
> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> nmake install
> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin
>
> @echo PySide build pyside release
> cd %PYSIDEDIR%
> mkdir buildrelease
> cd buildrelease
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> nmake install
> @echo PySide build pyside debug
> cd %PYSIDEDIR%
> mkdir builddebug
> cd builddebug
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> nmake install
> @echo PySide build pyside tools release
> cd %PYSIDETOOLSDIR%
> mkdir buildrelease
> cd buildrelease
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> nmake install
>
> @echo PySide build pyside tools debug
> cd %PYSIDETOOLSDIR%
> mkdir builddebug
> cd builddebug
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> nmake install
>
> cd %PYSIDEINSTALLDIR%
> @echo Done building PySide Debug and Release version
>
>
> Regards,
> Bjørn Helge Kjøsnes
>
> On 05.09.2012 09:32, Chris Bartels wrote:
>> Hi all,
>>
>> Is there anyone who has succesfully build PySide Windows binaries with
>> qt 4.8? (If so, are they willing to share them?) I desperately need
>> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
>> haven't been able to build PySide.)
>>
>> Chris
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From bjelge at nefines.com  Wed Sep  5 10:05:01 2012
From: bjelge at nefines.com (=?ISO-8859-1?Q?Bj=F8rn_Helge_Kj=F8snes?=)
Date: Wed, 05 Sep 2012 10:05:01 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
	<504703A8.1030603@nefines.com>
	<CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>
Message-ID: <504707AD.3090907@nefines.com>

On 05.09.2012 09:57, Roman Lacko wrote:
> Hi Bjorn,
>
> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
>> Hi,
>>
>> I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I
>> have not made any packages but I can share my build batch file. I use
>> this batch file in a Visual Studio 2008 Command Prompt. You have to have
>> a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source
>> using Visula Studio 2008 if you want the debug versions as well as the
>> release version. I guess you can use the stock versions of but Qt and
>> Python if  you just remove the debug build parts of the batch file.
> Please can You send configure.exe parameters used when building Qt from source ?
> Thanks
>
>>
>> SET QTDIR=\Projects\Qt\QT482\
>> SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
>> SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
>> SET PYTHONVER=27
>> SET PYSIDESOURCEDIR=\Projects\PySide\
>> SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
>> SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
>> SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
>> SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
>> SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
>> SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
>> SET QTDIR=E:\Projects\QT\QT482
>> SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
>> SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
>> SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
>> SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\
>>
>> SET
>> PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%PATH%
>>
>> @echo make install dir
>> mkdir %PYSIDEINSTALLDIR%
>> @echo go to pyside source dir
>> cd %PYSIDESOURCEDIR%
>> @echo make install dir
>> mkdir %PSINSTALLR%
>>
>> @echo PySide build shiboken release
>> cd %SHIBOKENDIR%
>> mkdir buildrelease
>> cd buildrelease
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>> -DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe"
>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>> nmake install
>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
>> @echo PySide build shiboken debug
>> mkdir %PSINSTALLD%
>> cd %SHIBOKENDIR%
>> mkdir builddebug
>> cd builddebug
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>> -DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe"
>> -DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib"
>> -DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib"
>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>> nmake install
>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin
>>
>> @echo PySide build pyside release
>> cd %PYSIDEDIR%
>> mkdir buildrelease
>> cd buildrelease
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>> nmake install
>> @echo PySide build pyside debug
>> cd %PYSIDEDIR%
>> mkdir builddebug
>> cd builddebug
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>> nmake install
>> @echo PySide build pyside tools release
>> cd %PYSIDETOOLSDIR%
>> mkdir buildrelease
>> cd buildrelease
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>> nmake install
>>
>> @echo PySide build pyside tools debug
>> cd %PYSIDETOOLSDIR%
>> mkdir builddebug
>> cd builddebug
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>> nmake install
>>
>> cd %PYSIDEINSTALLDIR%
>> @echo Done building PySide Debug and Release version
>>
>>
>> Regards,
>> Bjørn Helge Kjøsnes
>>
>> On 05.09.2012 09:32, Chris Bartels wrote:
>>> Hi all,
>>>
>>> Is there anyone who has succesfully build PySide Windows binaries with
>>> qt 4.8? (If so, are they willing to share them?) I desperately need
>>> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
>>> haven't been able to build PySide.)
>>>
>>> Chris
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
Hi Roman,

I use this method when building my own Qt from source:



    Build QT latest version using Visual Studio 2008

 1. Make sure you have openssl library installed
     1. Download from http://www.slproweb.com/products/Win32OpenSSL.html
        and install the Win32 OpenSSL full package (current version is
        v1.0.0a)
     2. Install it to where you have the other libraries and let it
        install dll to windows system (my place is
        E:\Projects\OpenSSL-Win32)
 2. Download QT source. Latest version can be found with the name
    qt-everywhere-opensource-src-xxxx.zip
    <http://download.qt.nokia.com/qt/source/>.
 3. Unzip to a directory without spaces in the name like
    e:\projects\qt\qt482.
 4. Edit environment variable to add: QTDIR = e:\projects\qt\qt482
 5. Edit the PATH environment variable to add: %QTDIR%\bin
 6. Go to the e:\projects\qt\qt482 in Visual Studio 2008 command prompt
    and run:
     1. configure.exe -debug-and-release -platform win32-msvc2008
        -webkit -openssl -I E:\Projects\OpenSSL-Win32\Include -L
        E:\Projects\OpenSSL-Win32\Lib
 7. Open Visual Studio 2008 and ignore warnings as this is just demo
    apps with the same name in different directories
     1. Build debug
     2. Build release

Regards,
Bjørn Helge


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120905/e3126ee3/attachment.html>

From backup.rlacko at gmail.com  Wed Sep  5 10:10:24 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 5 Sep 2012 10:10:24 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <504707AD.3090907@nefines.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
	<504703A8.1030603@nefines.com>
	<CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>
	<504707AD.3090907@nefines.com>
Message-ID: <CAHC6v6j8-E_Uc7teesDDRznZdT9jXnyvFYcv-ZnU9oeK-tggGA@mail.gmail.com>

Bjorn, have You build also 64bit version of Qt and PySide ?

Thanks
R.

2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
> On 05.09.2012 09:57, Roman Lacko wrote:
>
> Hi Bjorn,
>
> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
>
> Hi,
>
> I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I
> have not made any packages but I can share my build batch file. I use
> this batch file in a Visual Studio 2008 Command Prompt. You have to have
> a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source
> using Visula Studio 2008 if you want the debug versions as well as the
> release version. I guess you can use the stock versions of but Qt and
> Python if  you just remove the debug build parts of the batch file.
>
> Please can You send configure.exe parameters used when building Qt from
> source ?
> Thanks
>
>
> SET QTDIR=\Projects\Qt\QT482\
> SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
> SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
> SET PYTHONVER=27
> SET PYSIDESOURCEDIR=\Projects\PySide\
> SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
> SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
> SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
> SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
> SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
> SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
> SET QTDIR=E:\Projects\QT\QT482
> SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
> SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
> SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
> SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\
>
> SET
> PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%PATH%
>
> @echo make install dir
> mkdir %PYSIDEINSTALLDIR%
> @echo go to pyside source dir
> cd %PYSIDESOURCEDIR%
> @echo make install dir
> mkdir %PSINSTALLR%
>
> @echo PySide build shiboken release
> cd %SHIBOKENDIR%
> mkdir buildrelease
> cd buildrelease
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
> -DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe"
> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> nmake install
> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
> @echo PySide build shiboken debug
> mkdir %PSINSTALLD%
> cd %SHIBOKENDIR%
> mkdir builddebug
> cd builddebug
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> -DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe"
> -DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib"
> -DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib"
> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> nmake install
> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin
>
> @echo PySide build pyside release
> cd %PYSIDEDIR%
> mkdir buildrelease
> cd buildrelease
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> nmake install
> @echo PySide build pyside debug
> cd %PYSIDEDIR%
> mkdir builddebug
> cd builddebug
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> nmake install
> @echo PySide build pyside tools release
> cd %PYSIDETOOLSDIR%
> mkdir buildrelease
> cd buildrelease
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> nmake install
>
> @echo PySide build pyside tools debug
> cd %PYSIDETOOLSDIR%
> mkdir builddebug
> cd builddebug
> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> nmake install
>
> cd %PYSIDEINSTALLDIR%
> @echo Done building PySide Debug and Release version
>
>
> Regards,
> Bjørn Helge Kjøsnes
>
> On 05.09.2012 09:32, Chris Bartels wrote:
>
> Hi all,
>
> Is there anyone who has succesfully build PySide Windows binaries with
> qt 4.8? (If so, are they willing to share them?) I desperately need
> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
> haven't been able to build PySide.)
>
> Chris
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
> Hi Roman,
>
> I use this method when building my own Qt from source:
>
>
>
> Build QT latest version using Visual Studio 2008
>
> Make sure you have openssl library installed
>
> Download from  http://www.slproweb.com/products/Win32OpenSSL.html and
> install the Win32 OpenSSL full package (current version is v1.0.0a)
> Install it to where you have the other libraries and let it install dll to
> windows system (my place is E:\Projects\OpenSSL-Win32)
>
> Download QT source. Latest version can be  found with the name
> qt-everywhere-opensource-src-xxxx.zip.
> Unzip to a directory without spaces in the name like e:\projects\qt\qt482.
> Edit environment variable to add: QTDIR = e:\projects\qt\qt482
> Edit the PATH environment variable to add: %QTDIR%\bin
> Go to the e:\projects\qt\qt482 in Visual Studio 2008 command prompt and run:
>
> configure.exe -debug-and-release -platform win32-msvc2008 -webkit -openssl
> -I E:\Projects\OpenSSL-Win32\Include -L E:\Projects\OpenSSL-Win32\Lib
>
> Open Visual Studio 2008 and ignore warnings as this is just demo apps with
> the same name in different directories
>
> Build debug
> Build release
>
> Regards,
> Bjørn Helge
>
>


From bjelge at nefines.com  Wed Sep  5 10:15:17 2012
From: bjelge at nefines.com (=?ISO-8859-1?Q?Bj=F8rn_Helge_Kj=F8snes?=)
Date: Wed, 05 Sep 2012 10:15:17 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <CAHC6v6j8-E_Uc7teesDDRznZdT9jXnyvFYcv-ZnU9oeK-tggGA@mail.gmail.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
	<504703A8.1030603@nefines.com>
	<CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>
	<504707AD.3090907@nefines.com>
	<CAHC6v6j8-E_Uc7teesDDRznZdT9jXnyvFYcv-ZnU9oeK-tggGA@mail.gmail.com>
Message-ID: <50470A15.8040700@nefines.com>

Hi,

sorry but I have never had the need for a 64 bit version. I was just 
happy that the 32 bit version now finally compiles without patches.

Bjorn Helge

On 05.09.2012 10:10, Roman Lacko wrote:
> Bjorn, have You build also 64bit version of Qt and PySide ?
>
> Thanks
> R.
>
> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
>> On 05.09.2012 09:57, Roman Lacko wrote:
>>
>> Hi Bjorn,
>>
>> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
>>
>> Hi,
>>
>> I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I
>> have not made any packages but I can share my build batch file. I use
>> this batch file in a Visual Studio 2008 Command Prompt. You have to have
>> a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source
>> using Visula Studio 2008 if you want the debug versions as well as the
>> release version. I guess you can use the stock versions of but Qt and
>> Python if  you just remove the debug build parts of the batch file.
>>
>> Please can You send configure.exe parameters used when building Qt from
>> source ?
>> Thanks
>>
>>
>> SET QTDIR=\Projects\Qt\QT482\
>> SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
>> SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
>> SET PYTHONVER=27
>> SET PYSIDESOURCEDIR=\Projects\PySide\
>> SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
>> SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
>> SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
>> SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
>> SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
>> SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
>> SET QTDIR=E:\Projects\QT\QT482
>> SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
>> SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
>> SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
>> SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\
>>
>> SET
>> PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%PATH%
>>
>> @echo make install dir
>> mkdir %PYSIDEINSTALLDIR%
>> @echo go to pyside source dir
>> cd %PYSIDESOURCEDIR%
>> @echo make install dir
>> mkdir %PSINSTALLR%
>>
>> @echo PySide build shiboken release
>> cd %SHIBOKENDIR%
>> mkdir buildrelease
>> cd buildrelease
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>> -DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe"
>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>> nmake install
>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
>> @echo PySide build shiboken debug
>> mkdir %PSINSTALLD%
>> cd %SHIBOKENDIR%
>> mkdir builddebug
>> cd builddebug
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>> -DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe"
>> -DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib"
>> -DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib"
>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>> nmake install
>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin
>>
>> @echo PySide build pyside release
>> cd %PYSIDEDIR%
>> mkdir buildrelease
>> cd buildrelease
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>> nmake install
>> @echo PySide build pyside debug
>> cd %PYSIDEDIR%
>> mkdir builddebug
>> cd builddebug
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>> nmake install
>> @echo PySide build pyside tools release
>> cd %PYSIDETOOLSDIR%
>> mkdir buildrelease
>> cd buildrelease
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>> nmake install
>>
>> @echo PySide build pyside tools debug
>> cd %PYSIDETOOLSDIR%
>> mkdir builddebug
>> cd builddebug
>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>> nmake install
>>
>> cd %PYSIDEINSTALLDIR%
>> @echo Done building PySide Debug and Release version
>>
>>
>> Regards,
>> Bjørn Helge Kjøsnes
>>
>> On 05.09.2012 09:32, Chris Bartels wrote:
>>
>> Hi all,
>>
>> Is there anyone who has succesfully build PySide Windows binaries with
>> qt 4.8? (If so, are they willing to share them?) I desperately need
>> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
>> haven't been able to build PySide.)
>>
>> Chris
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>> Hi Roman,
>>
>> I use this method when building my own Qt from source:
>>
>>
>>
>> Build QT latest version using Visual Studio 2008
>>
>> Make sure you have openssl library installed
>>
>> Download from  http://www.slproweb.com/products/Win32OpenSSL.html and
>> install the Win32 OpenSSL full package (current version is v1.0.0a)
>> Install it to where you have the other libraries and let it install dll to
>> windows system (my place is E:\Projects\OpenSSL-Win32)
>>
>> Download QT source. Latest version can be  found with the name
>> qt-everywhere-opensource-src-xxxx.zip.
>> Unzip to a directory without spaces in the name like e:\projects\qt\qt482.
>> Edit environment variable to add: QTDIR = e:\projects\qt\qt482
>> Edit the PATH environment variable to add: %QTDIR%\bin
>> Go to the e:\projects\qt\qt482 in Visual Studio 2008 command prompt and run:
>>
>> configure.exe -debug-and-release -platform win32-msvc2008 -webkit -openssl
>> -I E:\Projects\OpenSSL-Win32\Include -L E:\Projects\OpenSSL-Win32\Lib
>>
>> Open Visual Studio 2008 and ignore warnings as this is just demo apps with
>> the same name in different directories
>>
>> Build debug
>> Build release
>>
>> Regards,
>> Bjørn Helge
>>
>>



From backup.rlacko at gmail.com  Wed Sep  5 10:30:16 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 5 Sep 2012 10:30:16 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <50470A15.8040700@nefines.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>
	<504703A8.1030603@nefines.com>
	<CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>
	<504707AD.3090907@nefines.com>
	<CAHC6v6j8-E_Uc7teesDDRznZdT9jXnyvFYcv-ZnU9oeK-tggGA@mail.gmail.com>
	<50470A15.8040700@nefines.com>
Message-ID: <CAHC6v6gE_pFFsZyhBFJ5oQYpJZ=CNQr11BmEHW1s=4_Q-F83tg@mail.gmail.com>

OK, I will upload 32bit packages, and try to fix 64bit build.

Regards
Roman

2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
> Hi,
>
> sorry but I have never had the need for a 64 bit version. I was just happy
> that the 32 bit version now finally compiles without patches.
>
> Bjorn Helge
>
> On 05.09.2012 10:10, Roman Lacko wrote:
>>
>> Bjorn, have You build also 64bit version of Qt and PySide ?
>>
>> Thanks
>> R.
>>
>> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
>>>
>>> On 05.09.2012 09:57, Roman Lacko wrote:
>>>
>>> Hi Bjorn,
>>>
>>> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
>>>
>>> Hi,
>>>
>>> I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I
>>> have not made any packages but I can share my build batch file. I use
>>> this batch file in a Visual Studio 2008 Command Prompt. You have to have
>>> a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source
>>> using Visula Studio 2008 if you want the debug versions as well as the
>>> release version. I guess you can use the stock versions of but Qt and
>>> Python if  you just remove the debug build parts of the batch file.
>>>
>>> Please can You send configure.exe parameters used when building Qt from
>>> source ?
>>> Thanks
>>>
>>>
>>> SET QTDIR=\Projects\Qt\QT482\
>>> SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
>>> SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
>>> SET PYTHONVER=27
>>> SET PYSIDESOURCEDIR=\Projects\PySide\
>>> SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
>>> SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
>>> SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
>>> SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
>>> SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
>>> SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
>>> SET QTDIR=E:\Projects\QT\QT482
>>> SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
>>> SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
>>> SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
>>> SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\
>>>
>>> SET
>>>
>>> PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%PATH%
>>>
>>> @echo make install dir
>>> mkdir %PYSIDEINSTALLDIR%
>>> @echo go to pyside source dir
>>> cd %PYSIDESOURCEDIR%
>>> @echo make install dir
>>> mkdir %PSINSTALLR%
>>>
>>> @echo PySide build shiboken release
>>> cd %SHIBOKENDIR%
>>> mkdir buildrelease
>>> cd buildrelease
>>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>>> -DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe"
>>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
>>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
>>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
>>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
>>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>>> nmake install
>>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
>>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
>>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
>>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
>>> @echo PySide build shiboken debug
>>> mkdir %PSINSTALLD%
>>> cd %SHIBOKENDIR%
>>> mkdir builddebug
>>> cd builddebug
>>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>>> -DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe"
>>> -DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib"
>>> -DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib"
>>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
>>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
>>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
>>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
>>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>>> nmake install
>>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
>>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
>>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
>>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin
>>>
>>> @echo PySide build pyside release
>>> cd %PYSIDEDIR%
>>> mkdir buildrelease
>>> cd buildrelease
>>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>>> nmake install
>>> @echo PySide build pyside debug
>>> cd %PYSIDEDIR%
>>> mkdir builddebug
>>> cd builddebug
>>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>>> nmake install
>>> @echo PySide build pyside tools release
>>> cd %PYSIDETOOLSDIR%
>>> mkdir buildrelease
>>> cd buildrelease
>>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=FALSE
>>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
>>> nmake install
>>>
>>> @echo PySide build pyside tools debug
>>> cd %PYSIDETOOLSDIR%
>>> mkdir builddebug
>>> cd builddebug
>>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
>>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
>>> nmake install
>>>
>>> cd %PYSIDEINSTALLDIR%
>>> @echo Done building PySide Debug and Release version
>>>
>>>
>>> Regards,
>>> Bjørn Helge Kjøsnes
>>>
>>> On 05.09.2012 09:32, Chris Bartels wrote:
>>>
>>> Hi all,
>>>
>>> Is there anyone who has succesfully build PySide Windows binaries with
>>> qt 4.8? (If so, are they willing to share them?) I desperately need
>>> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
>>> haven't been able to build PySide.)
>>>
>>> Chris
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>> Hi Roman,
>>>
>>> I use this method when building my own Qt from source:
>>>
>>>
>>>
>>> Build QT latest version using Visual Studio 2008
>>>
>>> Make sure you have openssl library installed
>>>
>>> Download from  http://www.slproweb.com/products/Win32OpenSSL.html and
>>> install the Win32 OpenSSL full package (current version is v1.0.0a)
>>> Install it to where you have the other libraries and let it install dll
>>> to
>>> windows system (my place is E:\Projects\OpenSSL-Win32)
>>>
>>> Download QT source. Latest version can be  found with the name
>>> qt-everywhere-opensource-src-xxxx.zip.
>>> Unzip to a directory without spaces in the name like
>>> e:\projects\qt\qt482.
>>> Edit environment variable to add: QTDIR = e:\projects\qt\qt482
>>> Edit the PATH environment variable to add: %QTDIR%\bin
>>> Go to the e:\projects\qt\qt482 in Visual Studio 2008 command prompt and
>>> run:
>>>
>>> configure.exe -debug-and-release -platform win32-msvc2008 -webkit
>>> -openssl
>>> -I E:\Projects\OpenSSL-Win32\Include -L E:\Projects\OpenSSL-Win32\Lib
>>>
>>> Open Visual Studio 2008 and ignore warnings as this is just demo apps
>>> with
>>> the same name in different directories
>>>
>>> Build debug
>>> Build release
>>>
>>> Regards,
>>> Bjørn Helge
>>>
>>>
>


From tejashri.kandolkar at gmail.com  Thu Sep  6 06:09:36 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Thu, 6 Sep 2012 09:39:36 +0530
Subject: [PySide] Unable build PySide from Source on Linux
Message-ID: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>

Hi,

I am trying to build Pyside on Linux RHEL 64-bit machine.
I followed the steps mentioned @
http://qt-project.org/wiki/Building_PySide_on_Linux, but i face build
issues.

I got the source code for the same from
http://qt-project.org/wiki/PySideDownloads
and I only find PySide and Shiboken tar files (ApiExtractor and
generatorrunner directories are inside the Shiboken dir)

Just want to make sure if thats the correct way to build PySide from source?

I get the following error when I run cmake inside the PySide/build dir.
.........]$ cmake ..
-- The C compiler identification is GNU 4.4.4
-- The CXX compiler identification is GNU 4.4.4
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at CMakeLists.txt:8 (find_package):
  By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "GeneratorRunner", but CMake did not find one.

  Could not find a package configuration file provided by "GeneratorRunner"
  (requested version 0.6.16) with any of the following names:

    GeneratorRunnerConfig.cmake
    generatorrunner-config.cmake

  Add the installation prefix of "GeneratorRunner" to CMAKE_PREFIX_PATH or
  set "GeneratorRunner_DIR" to a directory containing one of the above
files.
  If "GeneratorRunner" provides a separate development package or SDK, be
  sure it has been installed.


-- Configuring incomplete, errors occurred!

Can anyone help on the proper build steps for building Pyside from Source?

Regards,
Tej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120906/7bf6ec1a/attachment.html>

From dev at projekt01.ch  Thu Sep  6 06:17:57 2012
From: dev at projekt01.ch (Roger)
Date: Thu, 6 Sep 2012 06:17:57 +0200
Subject: [PySide] windows builds pyside + qt 4.8
In-Reply-To: <CAHC6v6gE_pFFsZyhBFJ5oQYpJZ=CNQr11BmEHW1s=4_Q-F83tg@mail.gmail.com>
References: <CAKhYEFPawYk1xLbW0C00zeo3d3uJ_eJhD5xWUKsnKsqfkwpL8w@mail.gmail.com>	<504703A8.1030603@nefines.com>	<CAHC6v6iFxo=k2UM9xnqtVCn-4fX7i1Q6F8aDnSJ5u90y-Z5mHQ@mail.gmail.com>	<504707AD.3090907@nefines.com>	<CAHC6v6j8-E_Uc7teesDDRznZdT9jXnyvFYcv-ZnU9oeK-tggGA@mail.gmail.com>	<50470A15.8040700@nefines.com>
	<CAHC6v6gE_pFFsZyhBFJ5oQYpJZ=CNQr11BmEHW1s=4_Q-F83tg@mail.gmail.com>
Message-ID: <011601cd8be6$98dfdfc0$ca9f9f40$@projekt01.ch>

Hi Roman

> Betreff: Re: [PySide] windows builds pyside + qt 4.8
> 
> OK, I will upload 32bit packages, and try to fix 64bit build.

This whould be great. The missing 4.8 release is also what
we need for switch from PyQt to pyside. Because of bugs
in pyside Qt 4.7 WebKit.

Regards
Roger Ineichen

> Regards
> Roman
> 
> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
> > Hi,
> >
> > sorry but I have never had the need for a 64 bit version. I was just
happy
> > that the 32 bit version now finally compiles without patches.
> >
> > Bjorn Helge
> >
> > On 05.09.2012 10:10, Roman Lacko wrote:
> >>
> >> Bjorn, have You build also 64bit version of Qt and PySide ?
> >>
> >> Thanks
> >> R.
> >>
> >> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
> >>>
> >>> On 05.09.2012 09:57, Roman Lacko wrote:
> >>>
> >>> Hi Bjorn,
> >>>
> >>> 2012/9/5 Bjørn Helge Kjøsnes <bjelge at nefines.com>:
> >>>
> >>> Hi,
> >>>
> >>> I have successfully built PySide 1.1.2 with Qt 4.8.2 and Python 2.7. I
> >>> have not made any packages but I can share my build batch file. I use
> >>> this batch file in a Visual Studio 2008 Command Prompt. You have to
have
> >>> a Python build in Visual Studio 2008 and a Qt 4.8.2 build from source
> >>> using Visula Studio 2008 if you want the debug versions as well as the
> >>> release version. I guess you can use the stock versions of but Qt and
> >>> Python if  you just remove the debug build parts of the batch file.
> >>>
> >>> Please can You send configure.exe parameters used when building Qt
from
> >>> source ?
> >>> Thanks
> >>>
> >>>
> >>> SET QTDIR=\Projects\Qt\QT482\
> >>> SET PYTHONDDIR=\Projects\Python\Python-2.7.3\PCbuild\
> >>> SET PYTHONRDIR=\Projects\Python\Python-2.7.3\PCbuild\
> >>> SET PYTHONVER=27
> >>> SET PYSIDESOURCEDIR=\Projects\PySide\
> >>> SET PYSIDEINSTALLDIR=\Projects\PySide\PySideInstall\
> >>> SET PSINSTALLD=%PYSIDEINSTALLDIR%Debug
> >>> SET PSINSTALLR=%PYSIDEINSTALLDIR%Release
> >>> SET SHIBOKENDIR=\Projects\PySide\shiboken-1.1.2
> >>> SET PYSIDEDIR=\Projects\PySide\pyside-qt4.8+1.1.2
> >>> SET PYSIDETOOLSDIR=\Projects\PySide\pyside-tools-0.2.13
> >>> SET QTDIR=E:\Projects\QT\QT482
> >>> SET LIBXML=E:\Projects\PySide\libxml2-2.7.8.win32\
> >>> SET LIBXSLT=E:\Projects\PySide\libxslt-1.1.26.win32\
> >>> SET LIBICONV=E:\Projects\PySide\iconv-1.9.2.win32\
> >>> SET LIBZLIB=E:\Projects\PySide\zlib-1.2.5\
> >>>
> >>> SET
> >>>
> >>>
> PATH=%QTDIR%\bin;%LIBXML%bin;%LIBXSLT%bin;%LIBICONV%bin;%LIBZLIB%bin;%P
> ATH%
> >>>
> >>> @echo make install dir
> >>> mkdir %PYSIDEINSTALLDIR%
> >>> @echo go to pyside source dir
> >>> cd %PYSIDESOURCEDIR%
> >>> @echo make install dir
> >>> mkdir %PSINSTALLR%
> >>>
> >>> @echo PySide build shiboken release
> >>> cd %SHIBOKENDIR%
> >>> mkdir buildrelease
> >>> cd buildrelease
> >>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -
> DBUILD_TESTS=FALSE
> >>> -DPYTHON_EXECUTABLE="%PYTHONRDIR%python.exe"
> >>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
> >>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
> >>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
> >>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
> >>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> >>> nmake install
> >>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Release\bin
> >>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Release\bin
> >>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Release\bin
> >>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Release\bin
> >>> @echo PySide build shiboken debug
> >>> mkdir %PSINSTALLD%
> >>> cd %SHIBOKENDIR%
> >>> mkdir builddebug
> >>> cd builddebug
> >>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> >>> -DPYTHON_EXECUTABLE="%PYTHONDDIR%python_d.exe"
> >>> -DPYTHON_DEBUG_LIBRARY="%PYTHONDDIR%python%PYTHONVER%_d.lib"
> >>> -DPYTHON_LIBRARIES="%PYTHONDDIR%python%PYTHONVER%_d.lib"
> >>> -DLIBXML2_LIBRARIES=%LIBXML%lib\libxml2.lib
> >>> -DLIBXML2_INCLUDE_DIR=%LIBXML%include
> >>> -DLIBXSLT_LIBRARIES=%LIBXSLT%lib\libxslt.lib
> >>> -DLIBXSLT_INCLUDE_DIR=%LIBXSLT%include
> >>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> >>> nmake install
> >>> copy %LIBXML%bin\libxml2.dll %PYSIDEINSTALLDIR%Debug\bin
> >>> copy %LIBXSLT%bin\libxslt.dll %PYSIDEINSTALLDIR%Debug\bin
> >>> copy %LIBICONV%bin\iconv.dll %PYSIDEINSTALLDIR%Debug\bin
> >>> copy %LIBZLIB%bin\zlib1.dll %PYSIDEINSTALLDIR%Debug\bin
> >>>
> >>> @echo PySide build pyside release
> >>> cd %PYSIDEDIR%
> >>> mkdir buildrelease
> >>> cd buildrelease
> >>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -
> DBUILD_TESTS=FALSE
> >>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> >>> nmake install
> >>> @echo PySide build pyside debug
> >>> cd %PYSIDEDIR%
> >>> mkdir builddebug
> >>> cd builddebug
> >>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> >>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> >>> nmake install
> >>> @echo PySide build pyside tools release
> >>> cd %PYSIDETOOLSDIR%
> >>> mkdir buildrelease
> >>> cd buildrelease
> >>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -
> DBUILD_TESTS=FALSE
> >>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLR%" ..
> >>> nmake install
> >>>
> >>> @echo PySide build pyside tools debug
> >>> cd %PYSIDETOOLSDIR%
> >>> mkdir builddebug
> >>> cd builddebug
> >>> cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=FALSE
> >>> -DCMAKE_INSTALL_PREFIX="%PSINSTALLD%" ..
> >>> nmake install
> >>>
> >>> cd %PYSIDEINSTALLDIR%
> >>> @echo Done building PySide Debug and Release version
> >>>
> >>>
> >>> Regards,
> >>> Bjørn Helge Kjøsnes
> >>>
> >>> On 05.09.2012 09:32, Chris Bartels wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Is there anyone who has succesfully build PySide Windows binaries with
> >>> qt 4.8? (If so, are they willing to share them?) I desperately need
> >>> the 4.8 versions, as there are some crucial bugfixes in Qt 4.8.. but I
> >>> haven't been able to build PySide.)
> >>>
> >>> Chris
> >>> _______________________________________________
> >>> PySide mailing list
> >>> PySide at qt-project.org
> >>> http://lists.qt-project.org/mailman/listinfo/pyside
> >>>
> >>> _______________________________________________
> >>> PySide mailing list
> >>> PySide at qt-project.org
> >>> http://lists.qt-project.org/mailman/listinfo/pyside
> >>>
> >>> Hi Roman,
> >>>
> >>> I use this method when building my own Qt from source:
> >>>
> >>>
> >>>
> >>> Build QT latest version using Visual Studio 2008
> >>>
> >>> Make sure you have openssl library installed
> >>>
> >>> Download from  http://www.slproweb.com/products/Win32OpenSSL.html and
> >>> install the Win32 OpenSSL full package (current version is v1.0.0a)
> >>> Install it to where you have the other libraries and let it install
dll
> >>> to
> >>> windows system (my place is E:\Projects\OpenSSL-Win32)
> >>>
> >>> Download QT source. Latest version can be  found with the name
> >>> qt-everywhere-opensource-src-xxxx.zip.
> >>> Unzip to a directory without spaces in the name like
> >>> e:\projects\qt\qt482.
> >>> Edit environment variable to add: QTDIR = e:\projects\qt\qt482
> >>> Edit the PATH environment variable to add: %QTDIR%\bin
> >>> Go to the e:\projects\qt\qt482 in Visual Studio 2008 command prompt
and
> >>> run:
> >>>
> >>> configure.exe -debug-and-release -platform win32-msvc2008 -webkit
> >>> -openssl
> >>> -I E:\Projects\OpenSSL-Win32\Include -L E:\Projects\OpenSSL-Win32\Lib
> >>>
> >>> Open Visual Studio 2008 and ignore warnings as this is just demo apps
> >>> with
> >>> the same name in different directories
> >>>
> >>> Build debug
> >>> Build release
> >>>
> >>> Regards,
> >>> Bjørn Helge
> >>>
> >>>
> >
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside




From backup.rlacko at gmail.com  Thu Sep  6 08:26:20 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Thu, 6 Sep 2012 08:26:20 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
Message-ID: <CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>

Hi,

here is another option how to build PySide from source on Linux [1].
There is known bug when building with python 3.2 that i will fix in
next release.

Regards
R.

[1] http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts

2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi,
>
> I am trying to build Pyside on Linux RHEL 64-bit machine.
> I followed the steps mentioned @
> http://qt-project.org/wiki/Building_PySide_on_Linux, but i face build
> issues.
>
> I got the source code for the same from
> http://qt-project.org/wiki/PySideDownloads
> and I only find PySide and Shiboken tar files (ApiExtractor and
> generatorrunner directories are inside the Shiboken dir)
>
> Just want to make sure if thats the correct way to build PySide from source?
>
> I get the following error when I run cmake inside the PySide/build dir.
> .........]$ cmake ..
> -- The C compiler identification is GNU 4.4.4
> -- The CXX compiler identification is GNU 4.4.4
> -- Check for working C compiler: /usr/bin/gcc
> -- Check for working C compiler: /usr/bin/gcc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> CMake Error at CMakeLists.txt:8 (find_package):
>   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH this
>   project has asked CMake to find a package configuration file provided by
>   "GeneratorRunner", but CMake did not find one.
>
>   Could not find a package configuration file provided by "GeneratorRunner"
>   (requested version 0.6.16) with any of the following names:
>
>     GeneratorRunnerConfig.cmake
>     generatorrunner-config.cmake
>
>   Add the installation prefix of "GeneratorRunner" to CMAKE_PREFIX_PATH or
>   set "GeneratorRunner_DIR" to a directory containing one of the above
> files.
>   If "GeneratorRunner" provides a separate development package or SDK, be
>   sure it has been installed.
>
>
> -- Configuring incomplete, errors occurred!
>
> Can anyone help on the proper build steps for building Pyside from Source?
>
> Regards,
> Tej
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From greatrgb at gmail.com  Thu Sep  6 17:03:29 2012
From: greatrgb at gmail.com (Tony Barbieri)
Date: Thu, 6 Sep 2012 11:03:29 -0400
Subject: [PySide] QNetworkCookieJar issue
Message-ID: <CAJhmvsQz3vBT86viyXSLNETV6mJ_vo8VzJMeqc9G59_ENwuSzA@mail.gmail.com>

Hello,

I am trying to execute QNetworkCookieJar.setAllCookies but I keep getting
an error:

TypeError: 'PySide.QtNetwork.QNetworkCookieJar.setAllCookies' called with
wrong argument types:
  PySide.QtNetwork.QNetworkCookieJar.setAllCookies(list)
Supported signatures:
  PySide.QtNetwork.QNetworkCookieJar.setAllCookies(list)

I am indeed passing a list in, it says to expect a QList but QList isn't
available in PySide correct?  I should be using the python list type, yea?

Thanks!

-- 
-tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120906/c2cea19a/attachment.html>

From pyside at m.allo.ws  Thu Sep  6 19:18:54 2012
From: pyside at m.allo.ws (Zak)
Date: Thu, 06 Sep 2012 13:18:54 -0400
Subject: [PySide] PySide plus Django: How can I make the PySide
 application auto-start the server?
In-Reply-To: <503E365C.8050808@bluewin.ch>
References: <503D1C2F.2000002@m.allo.ws> <503D43A3.2080707@m.allo.ws>
	<503D9244.7000606@bluewin.ch> <503E2094.2040609@m.allo.ws>
	<503E365C.8050808@bluewin.ch>
Message-ID: <5048DAFE.1050608@m.allo.ws>

To see my full solution, look at the code below. Here it is described in 
English:

Use the Windows command 'tasklist' to get a list of all running 
processes. Unfortunately, several processes are named simply 
'python.exe', and I could not find a way to figure out which one 
corresponded to manage.py. If you kill the wrong 'python.exe' process, a 
process may essentially kill itself. If the process kills itself before 
it kills manage.py, then manage.py will not be killed at all.

To solve this problem, I ran 'tasklist' several times and kept track of 
when new processes appeared and which PID they had. It turns out that 
three 'python.exe' processes are created, and you need to kill the third 
one.

I eventually kill the process using 'taskkill /F /pid %s' % (pid_to_kill).

Here is the code, simplified and merged into a single file:

import re
import subprocess

pyPat = re.compile("(?m)^python\.exe\s+(?P<pid>\d+)")
# pyPat matches if "python.exe" occurs at the start of a new line (not in
# the middle), followed by one or more spaces, followed by one or more
# digits. The digits are stored in the 'pid' group of the match object.

def get_python_pids():
     tasklist = subprocess.check_output(["tasklist"])
     pids = []
     for mtch in pyPat.finditer(tasklist):
         pids.append(mtch.group('pid'))
     return pids


import sys
import subprocess
from PySide.QtCore import *
from PySide.QtGui import *
from PySide.QtWebKit import *


# Create a Qt application
app = QApplication(sys.argv)
# Create a browser window and show it
browser = QWebView(None)
browser.load(QUrl("http://127.0.0.1:8000/"))
browser.show()

# pids = pm.get_python_pids()
# print "PID list 1:"
# print pids
## Assuming no other Python things are running,
## this prints a list of one PID, e.g. ['1']

# Start the Django server
manage_path = local_settings.root_dir + 'manage.py'
server = subprocess.Popen(["python", manage_path, "runserver"])

pids_1 = pm.get_python_pids()
# print "PID list 2:"
# print pids_1
## Prints a list of two PIDs, e.g. ['1', '2']

# Enter Qt application main loop
app.exec_()

# If execution reaches this point, then the GUI window was closed

# To kill the Django server, we must first figure out what
# its Windows PID is

pids_2 = pm.get_python_pids()
# print "PID list 3:"
# print pids_2
## Prints a list of three PIDs, e.g. ['1', '2', '3']
## The proper process to kill is whichever one is new in pids_2. That is to
## say, we should kill the process which is listed in pids_2 but is not
## present in pids_1. In this example, it would be PID '3'.

# max_kill is the maximum number of processes named 'python.exe' to kill
max_kill = 1
for pid in pids_2:
     if pid in pids_1:
         continue
     else:
         subprocess.call(["taskkill", "/F", "/pid", pid])
         max_kill -= 1
     if max_kill == 0:
         break

# Now exit Python entirely
sys.exit()

Zak F.


From greatrgb at gmail.com  Thu Sep  6 20:08:16 2012
From: greatrgb at gmail.com (Tony Barbieri)
Date: Thu, 6 Sep 2012 14:08:16 -0400
Subject: [PySide] QNetworkCookieJar issue
In-Reply-To: <CAJhmvsQz3vBT86viyXSLNETV6mJ_vo8VzJMeqc9G59_ENwuSzA@mail.gmail.com>
References: <CAJhmvsQz3vBT86viyXSLNETV6mJ_vo8VzJMeqc9G59_ENwuSzA@mail.gmail.com>
Message-ID: <CAJhmvsSM19h0nEGjDRqtFV+aa0r07H4AWmJ139HUan_+7uQoMw@mail.gmail.com>

Nevermind....I was doing something stupid.  Sorry for the noise.

-tony

On Thu, Sep 6, 2012 at 11:03 AM, Tony Barbieri <greatrgb at gmail.com> wrote:

> Hello,
>
> I am trying to execute QNetworkCookieJar.setAllCookies but I keep getting
> an error:
>
> TypeError: 'PySide.QtNetwork.QNetworkCookieJar.setAllCookies' called with
> wrong argument types:
>   PySide.QtNetwork.QNetworkCookieJar.setAllCookies(list)
> Supported signatures:
>   PySide.QtNetwork.QNetworkCookieJar.setAllCookies(list)
>
> I am indeed passing a list in, it says to expect a QList but QList isn't
> available in PySide correct?  I should be using the python list type, yea?
>
> Thanks!
>
> --
> -tony
>



-- 
-tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120906/a750f8f6/attachment.html>

From joao.vale at ndrive.com  Fri Sep  7 10:33:46 2012
From: joao.vale at ndrive.com (=?UTF-8?Q?Jo=C3=A3o_Vale?=)
Date: Fri, 7 Sep 2012 09:33:46 +0100
Subject: [PySide] PySide plus Django: How can I make the PySide
 application auto-start the server?
In-Reply-To: <5048DAFE.1050608@m.allo.ws>
References: <503D1C2F.2000002@m.allo.ws> <503D43A3.2080707@m.allo.ws>
	<503D9244.7000606@bluewin.ch> <503E2094.2040609@m.allo.ws>
	<503E365C.8050808@bluewin.ch> <5048DAFE.1050608@m.allo.ws>
Message-ID: <CAB93VtfV+H_8GkNKEyyYvwozM2PQ5FyAhTEVEXnJp8OsWFZL8Q@mail.gmail.com>

Hi,

I think you're overcomplicating things when looking up Django's PID, the
object returned by Popen already provides you that:

http://docs.python.org/library/subprocess.html#subprocess.Popen.pid

Cheers,
João



On Thu, Sep 6, 2012 at 6:18 PM, Zak <pyside at m.allo.ws> wrote:

> To see my full solution, look at the code below. Here it is described in
> English:
>
> Use the Windows command 'tasklist' to get a list of all running
> processes. Unfortunately, several processes are named simply
> 'python.exe', and I could not find a way to figure out which one
> corresponded to manage.py. If you kill the wrong 'python.exe' process, a
> process may essentially kill itself. If the process kills itself before
> it kills manage.py, then manage.py will not be killed at all.
>
> To solve this problem, I ran 'tasklist' several times and kept track of
> when new processes appeared and which PID they had. It turns out that
> three 'python.exe' processes are created, and you need to kill the third
> one.
>
> I eventually kill the process using 'taskkill /F /pid %s' % (pid_to_kill).
>
> Here is the code, simplified and merged into a single file:
>
> import re
> import subprocess
>
> pyPat = re.compile("(?m)^python\.exe\s+(?P<pid>\d+)")
> # pyPat matches if "python.exe" occurs at the start of a new line (not in
> # the middle), followed by one or more spaces, followed by one or more
> # digits. The digits are stored in the 'pid' group of the match object.
>
> def get_python_pids():
>      tasklist = subprocess.check_output(["tasklist"])
>      pids = []
>      for mtch in pyPat.finditer(tasklist):
>          pids.append(mtch.group('pid'))
>      return pids
>
>
> import sys
> import subprocess
> from PySide.QtCore import *
> from PySide.QtGui import *
> from PySide.QtWebKit import *
>
>
> # Create a Qt application
> app = QApplication(sys.argv)
> # Create a browser window and show it
> browser = QWebView(None)
> browser.load(QUrl("http://127.0.0.1:8000/"))
> browser.show()
>
> # pids = pm.get_python_pids()
> # print "PID list 1:"
> # print pids
> ## Assuming no other Python things are running,
> ## this prints a list of one PID, e.g. ['1']
>
> # Start the Django server
> manage_path = local_settings.root_dir + 'manage.py'
> server = subprocess.Popen(["python", manage_path, "runserver"])
>
> pids_1 = pm.get_python_pids()
> # print "PID list 2:"
> # print pids_1
> ## Prints a list of two PIDs, e.g. ['1', '2']
>
> # Enter Qt application main loop
> app.exec_()
>
> # If execution reaches this point, then the GUI window was closed
>
> # To kill the Django server, we must first figure out what
> # its Windows PID is
>
> pids_2 = pm.get_python_pids()
> # print "PID list 3:"
> # print pids_2
> ## Prints a list of three PIDs, e.g. ['1', '2', '3']
> ## The proper process to kill is whichever one is new in pids_2. That is to
> ## say, we should kill the process which is listed in pids_2 but is not
> ## present in pids_1. In this example, it would be PID '3'.
>
> # max_kill is the maximum number of processes named 'python.exe' to kill
> max_kill = 1
> for pid in pids_2:
>      if pid in pids_1:
>          continue
>      else:
>          subprocess.call(["taskkill", "/F", "/pid", pid])
>          max_kill -= 1
>      if max_kill == 0:
>          break
>
> # Now exit Python entirely
> sys.exit()
>
> Zak F.
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120907/26c3bbfe/attachment.html>

From pyside at m.allo.ws  Fri Sep  7 19:20:28 2012
From: pyside at m.allo.ws (Zak)
Date: Fri, 07 Sep 2012 13:20:28 -0400
Subject: [PySide] PySide plus Django: How can I make the PySide
 application auto-start the server?
In-Reply-To: <CAB93VtfV+H_8GkNKEyyYvwozM2PQ5FyAhTEVEXnJp8OsWFZL8Q@mail.gmail.com>
References: <503D1C2F.2000002@m.allo.ws> <503D43A3.2080707@m.allo.ws>
	<503D9244.7000606@bluewin.ch> <503E2094.2040609@m.allo.ws>
	<503E365C.8050808@bluewin.ch> <5048DAFE.1050608@m.allo.ws>
	<CAB93VtfV+H_8GkNKEyyYvwozM2PQ5FyAhTEVEXnJp8OsWFZL8Q@mail.gmail.com>
Message-ID: <504A2CDC.2070001@m.allo.ws>

Thanks for the suggestion. Although it seems like it should work, it 
does not, it returns the wrong PID. I tried it. In the following 
example, the correct PID to kill is '3', but subprocess.Popen.pid 
(a.k.a. server.pid) returns '2'. Here is a shortened example:

import sys
import subprocess
from PySide.QtCore import *
from PySide.QtGui import *
from PySide.QtWebKit import *

# Create a Qt application
app = QApplication(sys.argv)

pids = pm.get_python_pids()
print "PID list 1:"
print pids
## Assuming no other Python things are running,
## this prints a list of one PID, e.g. ['1']

# Start the Django server
server = subprocess.Popen(["python", manage_path, "runserver"])

pids_1 = pm.get_python_pids()
print "PID list 2:"
print pids_1
## Prints a list of two PIDs, e.g. ['1', '2']

# Enter Qt application main loop
app.exec_()

# If execution reaches this point, then the GUI window was closed

# To kill the Django server, we must first figure out what
# its Windows PID is

pids_2 = pm.get_python_pids()
print "PID list 3:"
print pids_2
## Prints a list of three PIDs, e.g. ['1', '2', '3']
## The proper process to kill is whichever one is new in pids_2. That is to
## say, we should kill the process which is listed in pids_2 but is not
## present in pids_1. In this example, it would be PID '3'.

## Another idea to find the PID to kill:
print "Server PID:"
print server.pid
## This doesn't work. In the current example, this prints '2'.
## '2' is not the correct PID to kill, the correct PID
## is '3' in this example.

# max_kill is the maximum number of processes named 'python.exe' to kill
max_kill = 1
for pid in pids_2:
     if pid in pids_1:
         continue
     else:
         subprocess.call(["taskkill", "/F", "/pid", pid])
         max_kill -= 1
     if max_kill == 0:
         break

# Now exit Python entirely
sys.exit()

Trying to kill the Django server in this way is equivalent to 
server.kill() or server.terminate() or server.send_signal(CTRL_C_EVENT). 
The problem with those three is the same: they send the signal to PID 
'2', which is simply not the PID of the Django server. It is the PID 
bound to the Popen instance, but that is not correct.

Zak F.

On 9/7/12 4:33 AM, João Vale wrote:
> Hi,
>
> I think you're overcomplicating things when looking up Django's PID, 
> the object returned by Popen already provides you that:
>
> http://docs.python.org/library/subprocess.html#subprocess.Popen.pid
>
> Cheers,
> João
>
>
>
> On Thu, Sep 6, 2012 at 6:18 PM, Zak <pyside at m.allo.ws 
> <mailto:pyside at m.allo.ws>> wrote:
>
>     To see my full solution, look at the code below. Here it is
>     described in
>     English:
>
>     Use the Windows command 'tasklist' to get a list of all running
>     processes. Unfortunately, several processes are named simply
>     'python.exe', and I could not find a way to figure out which one
>     corresponded to manage.py. If you kill the wrong 'python.exe'
>     process, a
>     process may essentially kill itself. If the process kills itself
>     before
>     it kills manage.py, then manage.py will not be killed at all.
>
>     To solve this problem, I ran 'tasklist' several times and kept
>     track of
>     when new processes appeared and which PID they had. It turns out that
>     three 'python.exe' processes are created, and you need to kill the
>     third
>     one.
>
>     I eventually kill the process using 'taskkill /F /pid %s' %
>     (pid_to_kill).
>
>     Here is the code, simplified and merged into a single file:
>
>     import re
>     import subprocess
>
>     pyPat = re.compile("(?m)^python\.exe\s+(?P<pid>\d+)")
>     # pyPat matches if "python.exe" occurs at the start of a new line
>     (not in
>     # the middle), followed by one or more spaces, followed by one or more
>     # digits. The digits are stored in the 'pid' group of the match
>     object.
>
>     def get_python_pids():
>          tasklist = subprocess.check_output(["tasklist"])
>          pids = []
>          for mtch in pyPat.finditer(tasklist):
>              pids.append(mtch.group('pid'))
>          return pids
>
>
>     import sys
>     import subprocess
>     from PySide.QtCore import *
>     from PySide.QtGui import *
>     from PySide.QtWebKit import *
>
>
>     # Create a Qt application
>     app = QApplication(sys.argv)
>     # Create a browser window and show it
>     browser = QWebView(None)
>     browser.load(QUrl("http://127.0.0.1:8000/"))
>     browser.show()
>
>     # pids = pm.get_python_pids()
>     # print "PID list 1:"
>     # print pids
>     ## Assuming no other Python things are running,
>     ## this prints a list of one PID, e.g. ['1']
>
>     # Start the Django server
>     manage_path = local_settings.root_dir + 'manage.py'
>     server = subprocess.Popen(["python", manage_path, "runserver"])
>
>     pids_1 = pm.get_python_pids()
>     # print "PID list 2:"
>     # print pids_1
>     ## Prints a list of two PIDs, e.g. ['1', '2']
>
>     # Enter Qt application main loop
>     app.exec_()
>
>     # If execution reaches this point, then the GUI window was closed
>
>     # To kill the Django server, we must first figure out what
>     # its Windows PID is
>
>     pids_2 = pm.get_python_pids()
>     # print "PID list 3:"
>     # print pids_2
>     ## Prints a list of three PIDs, e.g. ['1', '2', '3']
>     ## The proper process to kill is whichever one is new in pids_2.
>     That is to
>     ## say, we should kill the process which is listed in pids_2 but
>     is not
>     ## present in pids_1. In this example, it would be PID '3'.
>
>     # max_kill is the maximum number of processes named 'python.exe'
>     to kill
>     max_kill = 1
>     for pid in pids_2:
>          if pid in pids_1:
>              continue
>          else:
>              subprocess.call(["taskkill", "/F", "/pid", pid])
>              max_kill -= 1
>          if max_kill == 0:
>              break
>
>     # Now exit Python entirely
>     sys.exit()
>
>     Zak F.
>     _______________________________________________
>     PySide mailing list
>     PySide at qt-project.org <mailto:PySide at qt-project.org>
>     http://lists.qt-project.org/mailman/listinfo/pyside
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120907/7411e76b/attachment.html>

From tejashri.kandolkar at gmail.com  Mon Sep 10 08:41:39 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Mon, 10 Sep 2012 12:11:39 +0530
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
Message-ID: <CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>

Hi,

Thanks, I haven't tried building it again yet, but will be trying it soon.
Also, can I have a rough idea of when the next release(with the python3.2
related bug fixed) will be available?

Because, ultimately I have to use Pyhon3.2.

Regards,
Tej

On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:

> Hi,
>
> here is another option how to build PySide from source on Linux [1].
> There is known bug when building with python 3.2 that i will fix in
> next release.
>
> Regards
> R.
>
> [1]
> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>
> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> > Hi,
> >
> > I am trying to build Pyside on Linux RHEL 64-bit machine.
> > I followed the steps mentioned @
> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face build
> > issues.
> >
> > I got the source code for the same from
> > http://qt-project.org/wiki/PySideDownloads
> > and I only find PySide and Shiboken tar files (ApiExtractor and
> > generatorrunner directories are inside the Shiboken dir)
> >
> > Just want to make sure if thats the correct way to build PySide from
> source?
> >
> > I get the following error when I run cmake inside the PySide/build dir.
> > .........]$ cmake ..
> > -- The C compiler identification is GNU 4.4.4
> > -- The CXX compiler identification is GNU 4.4.4
> > -- Check for working C compiler: /usr/bin/gcc
> > -- Check for working C compiler: /usr/bin/gcc -- works
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - done
> > -- Check for working CXX compiler: /usr/bin/c++
> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> > -- Detecting CXX compiler ABI info
> > -- Detecting CXX compiler ABI info - done
> > CMake Error at CMakeLists.txt:8 (find_package):
> >   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH this
> >   project has asked CMake to find a package configuration file provided
> by
> >   "GeneratorRunner", but CMake did not find one.
> >
> >   Could not find a package configuration file provided by
> "GeneratorRunner"
> >   (requested version 0.6.16) with any of the following names:
> >
> >     GeneratorRunnerConfig.cmake
> >     generatorrunner-config.cmake
> >
> >   Add the installation prefix of "GeneratorRunner" to CMAKE_PREFIX_PATH
> or
> >   set "GeneratorRunner_DIR" to a directory containing one of the above
> > files.
> >   If "GeneratorRunner" provides a separate development package or SDK, be
> >   sure it has been installed.
> >
> >
> > -- Configuring incomplete, errors occurred!
> >
> > Can anyone help on the proper build steps for building Pyside from
> Source?
> >
> > Regards,
> > Tej
> >
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120910/d831a3ba/attachment.html>

From tejashri.kandolkar at gmail.com  Mon Sep 10 08:44:21 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Mon, 10 Sep 2012 12:14:21 +0530
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
Message-ID: <CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>

Also, another question that I had was that is the build successful with
Python 3.1 (on Win7 32/64 and Linux 64bit?)

Regards,
Tej

On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar <
tejashri.kandolkar at gmail.com> wrote:

> Hi,
>
> Thanks, I haven't tried building it again yet, but will be trying it soon.
> Also, can I have a rough idea of when the next release(with the python3.2
> related bug fixed) will be available?
>
> Because, ultimately I have to use Pyhon3.2.
>
> Regards,
> Tej
>
>
> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>
>> Hi,
>>
>> here is another option how to build PySide from source on Linux [1].
>> There is known bug when building with python 3.2 that i will fix in
>> next release.
>>
>> Regards
>> R.
>>
>> [1]
>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>
>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> > Hi,
>> >
>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>> > I followed the steps mentioned @
>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face build
>> > issues.
>> >
>> > I got the source code for the same from
>> > http://qt-project.org/wiki/PySideDownloads
>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>> > generatorrunner directories are inside the Shiboken dir)
>> >
>> > Just want to make sure if thats the correct way to build PySide from
>> source?
>> >
>> > I get the following error when I run cmake inside the PySide/build dir.
>> > .........]$ cmake ..
>> > -- The C compiler identification is GNU 4.4.4
>> > -- The CXX compiler identification is GNU 4.4.4
>> > -- Check for working C compiler: /usr/bin/gcc
>> > -- Check for working C compiler: /usr/bin/gcc -- works
>> > -- Detecting C compiler ABI info
>> > -- Detecting C compiler ABI info - done
>> > -- Check for working CXX compiler: /usr/bin/c++
>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>> > -- Detecting CXX compiler ABI info
>> > -- Detecting CXX compiler ABI info - done
>> > CMake Error at CMakeLists.txt:8 (find_package):
>> >   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH this
>> >   project has asked CMake to find a package configuration file provided
>> by
>> >   "GeneratorRunner", but CMake did not find one.
>> >
>> >   Could not find a package configuration file provided by
>> "GeneratorRunner"
>> >   (requested version 0.6.16) with any of the following names:
>> >
>> >     GeneratorRunnerConfig.cmake
>> >     generatorrunner-config.cmake
>> >
>> >   Add the installation prefix of "GeneratorRunner" to CMAKE_PREFIX_PATH
>> or
>> >   set "GeneratorRunner_DIR" to a directory containing one of the above
>> > files.
>> >   If "GeneratorRunner" provides a separate development package or SDK,
>> be
>> >   sure it has been installed.
>> >
>> >
>> > -- Configuring incomplete, errors occurred!
>> >
>> > Can anyone help on the proper build steps for building Pyside from
>> Source?
>> >
>> > Regards,
>> > Tej
>> >
>> > _______________________________________________
>> > PySide mailing list
>> > PySide at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/pyside
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120910/8dda718e/attachment.html>

From backup.rlacko at gmail.com  Mon Sep 10 08:46:44 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Mon, 10 Sep 2012 08:46:44 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
Message-ID: <CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>

Hi Tej,

the windows build will be available today or tomorrow, for python 2.7,
3.2 and also 3.3rc

Regards
Roman

2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Also, another question that I had was that is the build successful with
> Python 3.1 (on Win7 32/64 and Linux 64bit?)
>
> Regards,
> Tej
>
> On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
> <tejashri.kandolkar at gmail.com> wrote:
>>
>> Hi,
>>
>> Thanks, I haven't tried building it again yet, but will be trying it soon.
>> Also, can I have a rough idea of when the next release(with the python3.2
>> related bug fixed) will be available?
>>
>> Because, ultimately I have to use Pyhon3.2.
>>
>> Regards,
>> Tej
>>
>>
>> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <backup.rlacko at gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> here is another option how to build PySide from source on Linux [1].
>>> There is known bug when building with python 3.2 that i will fix in
>>> next release.
>>>
>>> Regards
>>> R.
>>>
>>> [1]
>>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>>
>>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> > Hi,
>>> >
>>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>>> > I followed the steps mentioned @
>>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face build
>>> > issues.
>>> >
>>> > I got the source code for the same from
>>> > http://qt-project.org/wiki/PySideDownloads
>>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>>> > generatorrunner directories are inside the Shiboken dir)
>>> >
>>> > Just want to make sure if thats the correct way to build PySide from
>>> > source?
>>> >
>>> > I get the following error when I run cmake inside the PySide/build dir.
>>> > .........]$ cmake ..
>>> > -- The C compiler identification is GNU 4.4.4
>>> > -- The CXX compiler identification is GNU 4.4.4
>>> > -- Check for working C compiler: /usr/bin/gcc
>>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>> > -- Detecting C compiler ABI info
>>> > -- Detecting C compiler ABI info - done
>>> > -- Check for working CXX compiler: /usr/bin/c++
>>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>> > -- Detecting CXX compiler ABI info
>>> > -- Detecting CXX compiler ABI info - done
>>> > CMake Error at CMakeLists.txt:8 (find_package):
>>> >   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH
>>> > this
>>> >   project has asked CMake to find a package configuration file provided
>>> > by
>>> >   "GeneratorRunner", but CMake did not find one.
>>> >
>>> >   Could not find a package configuration file provided by
>>> > "GeneratorRunner"
>>> >   (requested version 0.6.16) with any of the following names:
>>> >
>>> >     GeneratorRunnerConfig.cmake
>>> >     generatorrunner-config.cmake
>>> >
>>> >   Add the installation prefix of "GeneratorRunner" to CMAKE_PREFIX_PATH
>>> > or
>>> >   set "GeneratorRunner_DIR" to a directory containing one of the above
>>> > files.
>>> >   If "GeneratorRunner" provides a separate development package or SDK,
>>> > be
>>> >   sure it has been installed.
>>> >
>>> >
>>> > -- Configuring incomplete, errors occurred!
>>> >
>>> > Can anyone help on the proper build steps for building Pyside from
>>> > Source?
>>> >
>>> > Regards,
>>> > Tej
>>> >
>>> > _______________________________________________
>>> > PySide mailing list
>>> > PySide at qt-project.org
>>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>> >
>>
>>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From joao.vale at ndrive.com  Mon Sep 10 11:48:02 2012
From: joao.vale at ndrive.com (=?UTF-8?Q?Jo=C3=A3o_Vale?=)
Date: Mon, 10 Sep 2012 10:48:02 +0100
Subject: [PySide] PySide plus Django: How can I make the PySide
 application auto-start the server?
In-Reply-To: <504A2CDC.2070001@m.allo.ws>
References: <503D1C2F.2000002@m.allo.ws> <503D43A3.2080707@m.allo.ws>
	<503D9244.7000606@bluewin.ch> <503E2094.2040609@m.allo.ws>
	<503E365C.8050808@bluewin.ch> <5048DAFE.1050608@m.allo.ws>
	<CAB93VtfV+H_8GkNKEyyYvwozM2PQ5FyAhTEVEXnJp8OsWFZL8Q@mail.gmail.com>
	<504A2CDC.2070001@m.allo.ws>
Message-ID: <CAB93VtcykfBabX+gpgzbCTMyzt_gnLGJQXymuqmsDGSJjjAuEw@mail.gmail.com>

Hm, it's possible that Popen is creating some sort of "shell" and only then
starting the Django server. In that case, it might be the case that the PID
you're getting is the server's parent PID. In which case you can probably
find it by looking for a process with that specific parent PID.

Cheers,
João



On Fri, Sep 7, 2012 at 6:20 PM, Zak <pyside at m.allo.ws> wrote:

>  Thanks for the suggestion. Although it seems like it should work, it
> does not, it returns the wrong PID. I tried it. In the following example,
> the correct PID to kill is '3', but subprocess.Popen.pid (a.k.a.
> server.pid) returns '2'. Here is a shortened example:
>
>
> import sys
> import subprocess
> from PySide.QtCore import *
> from PySide.QtGui import *
> from PySide.QtWebKit import *
>
> # Create a Qt application
> app = QApplication(sys.argv)
>
> pids = pm.get_python_pids()
> print "PID list 1:"
>
> print pids
> ## Assuming no other Python things are running,
> ## this prints a list of one PID, e.g. ['1']
>
> # Start the Django server
> server = subprocess.Popen(["python", manage_path, "runserver"])
>
> pids_1 = pm.get_python_pids()
> print "PID list 2:"
>
> print pids_1
> ## Prints a list of two PIDs, e.g. ['1', '2']
>
> # Enter Qt application main loop
> app.exec_()
>
> # If execution reaches this point, then the GUI window was closed
>
> # To kill the Django server, we must first figure out what
> # its Windows PID is
>
> pids_2 = pm.get_python_pids()
> print "PID list 3:"
>
> print pids_2
> ## Prints a list of three PIDs, e.g. ['1', '2', '3']
> ## The proper process to kill is whichever one is new in pids_2. That is to
> ## say, we should kill the process which is listed in pids_2 but is not
> ## present in pids_1. In this example, it would be PID '3'.
>
> ## Another idea to find the PID to kill:
> print "Server PID:"
> print server.pid
> ## This doesn't work. In the current example, this prints '2'.
> ## '2' is not the correct PID to kill, the correct PID
> ## is '3' in this example.
>
>
> # max_kill is the maximum number of processes named 'python.exe' to kill
> max_kill = 1
> for pid in pids_2:
>     if pid in pids_1:
>         continue
>     else:
>         subprocess.call(["taskkill", "/F", "/pid", pid])
>         max_kill -= 1
>     if max_kill == 0:
>         break
>
> # Now exit Python entirely
> sys.exit()
>
> Trying to kill the Django server in this way is equivalent to
> server.kill() or server.terminate() or server.send_signal(CTRL_C_EVENT).
> The problem with those three is the same: they send the signal to PID '2',
> which is simply not the PID of the Django server. It is the PID bound to
> the Popen instance, but that is not correct.
>
> Zak F.
>
>
> On 9/7/12 4:33 AM, João Vale wrote:
>
> Hi,
>
>  I think you're overcomplicating things when looking up Django's PID, the
> object returned by Popen already provides you that:
>
>  http://docs.python.org/library/subprocess.html#subprocess.Popen.pid
>
>  Cheers,
> João
>
>
>
> On Thu, Sep 6, 2012 at 6:18 PM, Zak <pyside at m.allo.ws> wrote:
>
>> To see my full solution, look at the code below. Here it is described in
>> English:
>>
>> Use the Windows command 'tasklist' to get a list of all running
>> processes. Unfortunately, several processes are named simply
>> 'python.exe', and I could not find a way to figure out which one
>> corresponded to manage.py. If you kill the wrong 'python.exe' process, a
>> process may essentially kill itself. If the process kills itself before
>> it kills manage.py, then manage.py will not be killed at all.
>>
>> To solve this problem, I ran 'tasklist' several times and kept track of
>> when new processes appeared and which PID they had. It turns out that
>> three 'python.exe' processes are created, and you need to kill the third
>> one.
>>
>> I eventually kill the process using 'taskkill /F /pid %s' % (pid_to_kill).
>>
>> Here is the code, simplified and merged into a single file:
>>
>> import re
>> import subprocess
>>
>> pyPat = re.compile("(?m)^python\.exe\s+(?P<pid>\d+)")
>> # pyPat matches if "python.exe" occurs at the start of a new line (not in
>> # the middle), followed by one or more spaces, followed by one or more
>> # digits. The digits are stored in the 'pid' group of the match object.
>>
>> def get_python_pids():
>>      tasklist = subprocess.check_output(["tasklist"])
>>      pids = []
>>      for mtch in pyPat.finditer(tasklist):
>>          pids.append(mtch.group('pid'))
>>      return pids
>>
>>
>> import sys
>> import subprocess
>> from PySide.QtCore import *
>> from PySide.QtGui import *
>> from PySide.QtWebKit import *
>>
>>
>> # Create a Qt application
>> app = QApplication(sys.argv)
>> # Create a browser window and show it
>> browser = QWebView(None)
>> browser.load(QUrl("http://127.0.0.1:8000/"))
>> browser.show()
>>
>> # pids = pm.get_python_pids()
>> # print "PID list 1:"
>> # print pids
>> ## Assuming no other Python things are running,
>> ## this prints a list of one PID, e.g. ['1']
>>
>> # Start the Django server
>> manage_path = local_settings.root_dir + 'manage.py'
>> server = subprocess.Popen(["python", manage_path, "runserver"])
>>
>> pids_1 = pm.get_python_pids()
>> # print "PID list 2:"
>> # print pids_1
>> ## Prints a list of two PIDs, e.g. ['1', '2']
>>
>> # Enter Qt application main loop
>> app.exec_()
>>
>> # If execution reaches this point, then the GUI window was closed
>>
>> # To kill the Django server, we must first figure out what
>> # its Windows PID is
>>
>> pids_2 = pm.get_python_pids()
>> # print "PID list 3:"
>> # print pids_2
>> ## Prints a list of three PIDs, e.g. ['1', '2', '3']
>> ## The proper process to kill is whichever one is new in pids_2. That is
>> to
>> ## say, we should kill the process which is listed in pids_2 but is not
>> ## present in pids_1. In this example, it would be PID '3'.
>>
>> # max_kill is the maximum number of processes named 'python.exe' to kill
>> max_kill = 1
>> for pid in pids_2:
>>      if pid in pids_1:
>>          continue
>>      else:
>>          subprocess.call(["taskkill", "/F", "/pid", pid])
>>          max_kill -= 1
>>      if max_kill == 0:
>>          break
>>
>> # Now exit Python entirely
>> sys.exit()
>>
>> Zak F.
>>  _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120910/b239d486/attachment.html>

From bjelge at nefines.com  Mon Sep 10 12:33:09 2012
From: bjelge at nefines.com (=?ISO-8859-1?Q?Bj=F8rn_Helge_Kj=F8snes?=)
Date: Mon, 10 Sep 2012 12:33:09 +0200
Subject: [PySide] PySide plus Django: How can I make the PySide
 application auto-start the server?
In-Reply-To: <504A2CDC.2070001@m.allo.ws>
References: <503D1C2F.2000002@m.allo.ws> <503D43A3.2080707@m.allo.ws>
	<503D9244.7000606@bluewin.ch> <503E2094.2040609@m.allo.ws>
	<503E365C.8050808@bluewin.ch> <5048DAFE.1050608@m.allo.ws>
	<CAB93VtfV+H_8GkNKEyyYvwozM2PQ5FyAhTEVEXnJp8OsWFZL8Q@mail.gmail.com>
	<504A2CDC.2070001@m.allo.ws>
Message-ID: <504DC1E5.4090108@nefines.com>

Hi,

when you start Django development server with runserver, you are 
starting a process that listens for changes in the Django application 
and reloads the server each time a change is done to a file. If you just 
want the server to start without any reloading, you should add the 
--noreload to your popen. This way you get the real Django server 
process and not the process that listens for file changes and reload.

server = subprocess.Popen(["python", manage_path, "runserver","--noreload"])

https://docs.djangoproject.com/en/1.4/ref/django-admin/#django-admin-option---noreload

This works well for me. I am able to kill the server with the pid I get.

Regards,
Bjørn Helge Kjøsnes


On 07.09.2012 19:20, Zak wrote:
> Thanks for the suggestion. Although it seems like it should work, it 
> does not, it returns the wrong PID. I tried it. In the following 
> example, the correct PID to kill is '3', but subprocess.Popen.pid 
> (a.k.a. server.pid) returns '2'. Here is a shortened example:
>
> import sys
> import subprocess
> from PySide.QtCore import *
> from PySide.QtGui import *
> from PySide.QtWebKit import *
>
> # Create a Qt application
> app = QApplication(sys.argv)
>
> pids = pm.get_python_pids()
> print "PID list 1:"
> print pids
> ## Assuming no other Python things are running,
> ## this prints a list of one PID, e.g. ['1']
>
> # Start the Django server
> server = subprocess.Popen(["python", manage_path, "runserver"])
>
> pids_1 = pm.get_python_pids()
> print "PID list 2:"
> print pids_1
> ## Prints a list of two PIDs, e.g. ['1', '2']
>
> # Enter Qt application main loop
> app.exec_()
>
> # If execution reaches this point, then the GUI window was closed
>
> # To kill the Django server, we must first figure out what
> # its Windows PID is
>
> pids_2 = pm.get_python_pids()
> print "PID list 3:"
> print pids_2
> ## Prints a list of three PIDs, e.g. ['1', '2', '3']
> ## The proper process to kill is whichever one is new in pids_2. That 
> is to
> ## say, we should kill the process which is listed in pids_2 but is not
> ## present in pids_1. In this example, it would be PID '3'.
>
> ## Another idea to find the PID to kill:
> print "Server PID:"
> print server.pid
> ## This doesn't work. In the current example, this prints '2'.
> ## '2' is not the correct PID to kill, the correct PID
> ## is '3' in this example.
>
> # max_kill is the maximum number of processes named 'python.exe' to kill
> max_kill = 1
> for pid in pids_2:
>     if pid in pids_1:
>         continue
>     else:
>         subprocess.call(["taskkill", "/F", "/pid", pid])
>         max_kill -= 1
>     if max_kill == 0:
>         break
>
> # Now exit Python entirely
> sys.exit()
>
> Trying to kill the Django server in this way is equivalent to 
> server.kill() or server.terminate() or 
> server.send_signal(CTRL_C_EVENT). The problem with those three is the 
> same: they send the signal to PID '2', which is simply not the PID of 
> the Django server. It is the PID bound to the Popen instance, but that 
> is not correct.
>
> Zak F.
>
> On 9/7/12 4:33 AM, João Vale wrote:
>> Hi,
>>
>> I think you're overcomplicating things when looking up Django's PID, 
>> the object returned by Popen already provides you that:
>>
>> http://docs.python.org/library/subprocess.html#subprocess.Popen.pid
>>
>> Cheers,
>> João
>>
>>
>>
>> On Thu, Sep 6, 2012 at 6:18 PM, Zak <pyside at m.allo.ws 
>> <mailto:pyside at m.allo.ws>> wrote:
>>
>>     To see my full solution, look at the code below. Here it is
>>     described in
>>     English:
>>
>>     Use the Windows command 'tasklist' to get a list of all running
>>     processes. Unfortunately, several processes are named simply
>>     'python.exe', and I could not find a way to figure out which one
>>     corresponded to manage.py. If you kill the wrong 'python.exe'
>>     process, a
>>     process may essentially kill itself. If the process kills itself
>>     before
>>     it kills manage.py, then manage.py will not be killed at all.
>>
>>     To solve this problem, I ran 'tasklist' several times and kept
>>     track of
>>     when new processes appeared and which PID they had. It turns out that
>>     three 'python.exe' processes are created, and you need to kill
>>     the third
>>     one.
>>
>>     I eventually kill the process using 'taskkill /F /pid %s' %
>>     (pid_to_kill).
>>
>>     Here is the code, simplified and merged into a single file:
>>
>>     import re
>>     import subprocess
>>
>>     pyPat = re.compile("(?m)^python\.exe\s+(?P<pid>\d+)")
>>     # pyPat matches if "python.exe" occurs at the start of a new line
>>     (not in
>>     # the middle), followed by one or more spaces, followed by one or
>>     more
>>     # digits. The digits are stored in the 'pid' group of the match
>>     object.
>>
>>     def get_python_pids():
>>          tasklist = subprocess.check_output(["tasklist"])
>>          pids = []
>>          for mtch in pyPat.finditer(tasklist):
>>              pids.append(mtch.group('pid'))
>>          return pids
>>
>>
>>     import sys
>>     import subprocess
>>     from PySide.QtCore import *
>>     from PySide.QtGui import *
>>     from PySide.QtWebKit import *
>>
>>
>>     # Create a Qt application
>>     app = QApplication(sys.argv)
>>     # Create a browser window and show it
>>     browser = QWebView(None)
>>     browser.load(QUrl("http://127.0.0.1:8000/"))
>>     browser.show()
>>
>>     # pids = pm.get_python_pids()
>>     # print "PID list 1:"
>>     # print pids
>>     ## Assuming no other Python things are running,
>>     ## this prints a list of one PID, e.g. ['1']
>>
>>     # Start the Django server
>>     manage_path = local_settings.root_dir + 'manage.py'
>>     server = subprocess.Popen(["python", manage_path, "runserver"])
>>
>>     pids_1 = pm.get_python_pids()
>>     # print "PID list 2:"
>>     # print pids_1
>>     ## Prints a list of two PIDs, e.g. ['1', '2']
>>
>>     # Enter Qt application main loop
>>     app.exec_()
>>
>>     # If execution reaches this point, then the GUI window was closed
>>
>>     # To kill the Django server, we must first figure out what
>>     # its Windows PID is
>>
>>     pids_2 = pm.get_python_pids()
>>     # print "PID list 3:"
>>     # print pids_2
>>     ## Prints a list of three PIDs, e.g. ['1', '2', '3']
>>     ## The proper process to kill is whichever one is new in pids_2.
>>     That is to
>>     ## say, we should kill the process which is listed in pids_2 but
>>     is not
>>     ## present in pids_1. In this example, it would be PID '3'.
>>
>>     # max_kill is the maximum number of processes named 'python.exe'
>>     to kill
>>     max_kill = 1
>>     for pid in pids_2:
>>          if pid in pids_1:
>>              continue
>>          else:
>>              subprocess.call(["taskkill", "/F", "/pid", pid])
>>              max_kill -= 1
>>          if max_kill == 0:
>>              break
>>
>>     # Now exit Python entirely
>>     sys.exit()
>>
>>     Zak F.
>>     _______________________________________________
>>     PySide mailing list
>>     PySide at qt-project.org <mailto:PySide at qt-project.org>
>>     http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120910/67d92999/attachment.html>

From dennis.victorovich at gmail.com  Mon Sep 10 18:34:23 2012
From: dennis.victorovich at gmail.com (Dennis Victorovich)
Date: Mon, 10 Sep 2012 20:34:23 +0400
Subject: [PySide] Wrong PyObject reference counting leads to memory leak in
 QMap->PyDict converter template code of
 PySide/QtCore/typesystem_core_common.xml
Message-ID: <CAGrH=yrv6eV7UGNv57Nv4f_e_bUgQPrB9501nbsAzqb-hX0NUg@mail.gmail.com>

Hi everyone.

While migrating our project from PySide v1.0.9 to v1.1.1 we've spotted a
memory leak. (no leak with older 1.0.9 apiextractor and shiboken)

We've found and fixed small problem in conversion code in
PySide/QtCore/typesystem_core_common.xml.

We've checked our fix on ubuntu 32/64 and Win32 builds.
Problem is fixed, no memory leak.

Bug is reported https://bugreports.qt-project.org/browse/PYSIDE-107
Patch is attached.
Hope this will help.

Best regards.
Dennis Shilko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120910/28239397/attachment.html>

From tejashri.kandolkar at gmail.com  Tue Sep 11 12:59:58 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Tue, 11 Sep 2012 16:29:58 +0530
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
Message-ID: <CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>

Hi Roman,

I was able to build PySide successfully on Windows 7 with Python 2.7.
I now wanted to build it with Python 3.2..So wanted to know if the bug was
fixed and if PySide can now be built with Python3.2?

Also, how do I check if I am getting the latest released PySide code?
Is it that when I clone from github (without mentioning a version), it will
always get the latest release?

Regards,
Tej

On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>wrote:

> Hi Tej,
>
> the windows build will be available today or tomorrow, for python 2.7,
> 3.2 and also 3.3rc
>
> Regards
> Roman
>
> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> > Also, another question that I had was that is the build successful with
> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
> >
> > Regards,
> > Tej
> >
> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
> > <tejashri.kandolkar at gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Thanks, I haven't tried building it again yet, but will be trying it
> soon.
> >> Also, can I have a rough idea of when the next release(with the
> python3.2
> >> related bug fixed) will be available?
> >>
> >> Because, ultimately I have to use Pyhon3.2.
> >>
> >> Regards,
> >> Tej
> >>
> >>
> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <backup.rlacko at gmail.com>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> here is another option how to build PySide from source on Linux [1].
> >>> There is known bug when building with python 3.2 that i will fix in
> >>> next release.
> >>>
> >>> Regards
> >>> R.
> >>>
> >>> [1]
> >>>
> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
> >>>
> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>> > Hi,
> >>> >
> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
> >>> > I followed the steps mentioned @
> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
> build
> >>> > issues.
> >>> >
> >>> > I got the source code for the same from
> >>> > http://qt-project.org/wiki/PySideDownloads
> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
> >>> > generatorrunner directories are inside the Shiboken dir)
> >>> >
> >>> > Just want to make sure if thats the correct way to build PySide from
> >>> > source?
> >>> >
> >>> > I get the following error when I run cmake inside the PySide/build
> dir.
> >>> > .........]$ cmake ..
> >>> > -- The C compiler identification is GNU 4.4.4
> >>> > -- The CXX compiler identification is GNU 4.4.4
> >>> > -- Check for working C compiler: /usr/bin/gcc
> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
> >>> > -- Detecting C compiler ABI info
> >>> > -- Detecting C compiler ABI info - done
> >>> > -- Check for working CXX compiler: /usr/bin/c++
> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> >>> > -- Detecting CXX compiler ABI info
> >>> > -- Detecting CXX compiler ABI info - done
> >>> > CMake Error at CMakeLists.txt:8 (find_package):
> >>> >   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH
> >>> > this
> >>> >   project has asked CMake to find a package configuration file
> provided
> >>> > by
> >>> >   "GeneratorRunner", but CMake did not find one.
> >>> >
> >>> >   Could not find a package configuration file provided by
> >>> > "GeneratorRunner"
> >>> >   (requested version 0.6.16) with any of the following names:
> >>> >
> >>> >     GeneratorRunnerConfig.cmake
> >>> >     generatorrunner-config.cmake
> >>> >
> >>> >   Add the installation prefix of "GeneratorRunner" to
> CMAKE_PREFIX_PATH
> >>> > or
> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
> above
> >>> > files.
> >>> >   If "GeneratorRunner" provides a separate development package or
> SDK,
> >>> > be
> >>> >   sure it has been installed.
> >>> >
> >>> >
> >>> > -- Configuring incomplete, errors occurred!
> >>> >
> >>> > Can anyone help on the proper build steps for building Pyside from
> >>> > Source?
> >>> >
> >>> > Regards,
> >>> > Tej
> >>> >
> >>> > _______________________________________________
> >>> > PySide mailing list
> >>> > PySide at qt-project.org
> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
> >>> >
> >>
> >>
> >
> >
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120911/0fbc6d63/attachment.html>

From backup.rlacko at gmail.com  Tue Sep 11 13:14:53 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 11 Sep 2012 13:14:53 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
Message-ID: <CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>

Hi Tej,

2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi Roman,
>
> I was able to build PySide successfully on Windows 7 with Python 2.7.
> I now wanted to build it with Python 3.2..So wanted to know if the bug was
> fixed and if PySide can now be built with Python3.2?

Yes, all known bugs were fixed and You can build even with latest Python 3.3rc2

>
> Also, how do I check if I am getting the latest released PySide code?
> Is it that when I clone from github (without mentioning a version), it will
> always get the latest release?
>

The setup.py build script has two parameters that control version of
PySide modules cloned from git: --list-versions and --version.

For example to build latest stable version run:
python setup.py bdist --version=1.1.2 [...other params]

To build latest development version run:
python setup.py bdist --version=1.1.3dev [...other params]

To list all available versions run:
python setup.py --list-versions

Regards
Roman

> Regards,
> Tej
>
> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
> wrote:
>>
>> Hi Tej,
>>
>> the windows build will be available today or tomorrow, for python 2.7,
>> 3.2 and also 3.3rc
>>
>> Regards
>> Roman
>>
>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> > Also, another question that I had was that is the build successful with
>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>> >
>> > Regards,
>> > Tej
>> >
>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>> > <tejashri.kandolkar at gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> Thanks, I haven't tried building it again yet, but will be trying it
>> >> soon.
>> >> Also, can I have a rough idea of when the next release(with the
>> >> python3.2
>> >> related bug fixed) will be available?
>> >>
>> >> Because, ultimately I have to use Pyhon3.2.
>> >>
>> >> Regards,
>> >> Tej
>> >>
>> >>
>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <backup.rlacko at gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> here is another option how to build PySide from source on Linux [1].
>> >>> There is known bug when building with python 3.2 that i will fix in
>> >>> next release.
>> >>>
>> >>> Regards
>> >>> R.
>> >>>
>> >>> [1]
>> >>>
>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>> >>>
>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> >>> > Hi,
>> >>> >
>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>> >>> > I followed the steps mentioned @
>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>> >>> > build
>> >>> > issues.
>> >>> >
>> >>> > I got the source code for the same from
>> >>> > http://qt-project.org/wiki/PySideDownloads
>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>> >>> > generatorrunner directories are inside the Shiboken dir)
>> >>> >
>> >>> > Just want to make sure if thats the correct way to build PySide from
>> >>> > source?
>> >>> >
>> >>> > I get the following error when I run cmake inside the PySide/build
>> >>> > dir.
>> >>> > .........]$ cmake ..
>> >>> > -- The C compiler identification is GNU 4.4.4
>> >>> > -- The CXX compiler identification is GNU 4.4.4
>> >>> > -- Check for working C compiler: /usr/bin/gcc
>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>> >>> > -- Detecting C compiler ABI info
>> >>> > -- Detecting C compiler ABI info - done
>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>> >>> > -- Detecting CXX compiler ABI info
>> >>> > -- Detecting CXX compiler ABI info - done
>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>> >>> >   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH
>> >>> > this
>> >>> >   project has asked CMake to find a package configuration file
>> >>> > provided
>> >>> > by
>> >>> >   "GeneratorRunner", but CMake did not find one.
>> >>> >
>> >>> >   Could not find a package configuration file provided by
>> >>> > "GeneratorRunner"
>> >>> >   (requested version 0.6.16) with any of the following names:
>> >>> >
>> >>> >     GeneratorRunnerConfig.cmake
>> >>> >     generatorrunner-config.cmake
>> >>> >
>> >>> >   Add the installation prefix of "GeneratorRunner" to
>> >>> > CMAKE_PREFIX_PATH
>> >>> > or
>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>> >>> > above
>> >>> > files.
>> >>> >   If "GeneratorRunner" provides a separate development package or
>> >>> > SDK,
>> >>> > be
>> >>> >   sure it has been installed.
>> >>> >
>> >>> >
>> >>> > -- Configuring incomplete, errors occurred!
>> >>> >
>> >>> > Can anyone help on the proper build steps for building Pyside from
>> >>> > Source?
>> >>> >
>> >>> > Regards,
>> >>> > Tej
>> >>> >
>> >>> > _______________________________________________
>> >>> > PySide mailing list
>> >>> > PySide at qt-project.org
>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>> >>> >
>> >>
>> >>
>> >
>> >
>> > _______________________________________________
>> > PySide mailing list
>> > PySide at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/pyside
>> >
>
>


From backup.rlacko at gmail.com  Tue Sep 11 13:23:10 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 11 Sep 2012 13:23:10 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
Message-ID: <CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>

forgot to say that 64bit still does not build, just 32bit

R.

2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
> Hi Tej,
>
> 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> Hi Roman,
>>
>> I was able to build PySide successfully on Windows 7 with Python 2.7.
>> I now wanted to build it with Python 3.2..So wanted to know if the bug was
>> fixed and if PySide can now be built with Python3.2?
>
> Yes, all known bugs were fixed and You can build even with latest Python 3.3rc2
>
>>
>> Also, how do I check if I am getting the latest released PySide code?
>> Is it that when I clone from github (without mentioning a version), it will
>> always get the latest release?
>>
>
> The setup.py build script has two parameters that control version of
> PySide modules cloned from git: --list-versions and --version.
>
> For example to build latest stable version run:
> python setup.py bdist --version=1.1.2 [...other params]
>
> To build latest development version run:
> python setup.py bdist --version=1.1.3dev [...other params]
>
> To list all available versions run:
> python setup.py --list-versions
>
> Regards
> Roman
>
>> Regards,
>> Tej
>>
>> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
>> wrote:
>>>
>>> Hi Tej,
>>>
>>> the windows build will be available today or tomorrow, for python 2.7,
>>> 3.2 and also 3.3rc
>>>
>>> Regards
>>> Roman
>>>
>>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> > Also, another question that I had was that is the build successful with
>>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>>> >
>>> > Regards,
>>> > Tej
>>> >
>>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>>> > <tejashri.kandolkar at gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> Thanks, I haven't tried building it again yet, but will be trying it
>>> >> soon.
>>> >> Also, can I have a rough idea of when the next release(with the
>>> >> python3.2
>>> >> related bug fixed) will be available?
>>> >>
>>> >> Because, ultimately I have to use Pyhon3.2.
>>> >>
>>> >> Regards,
>>> >> Tej
>>> >>
>>> >>
>>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <backup.rlacko at gmail.com>
>>> >> wrote:
>>> >>>
>>> >>> Hi,
>>> >>>
>>> >>> here is another option how to build PySide from source on Linux [1].
>>> >>> There is known bug when building with python 3.2 that i will fix in
>>> >>> next release.
>>> >>>
>>> >>> Regards
>>> >>> R.
>>> >>>
>>> >>> [1]
>>> >>>
>>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>> >>>
>>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> >>> > Hi,
>>> >>> >
>>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>>> >>> > I followed the steps mentioned @
>>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>>> >>> > build
>>> >>> > issues.
>>> >>> >
>>> >>> > I got the source code for the same from
>>> >>> > http://qt-project.org/wiki/PySideDownloads
>>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>>> >>> > generatorrunner directories are inside the Shiboken dir)
>>> >>> >
>>> >>> > Just want to make sure if thats the correct way to build PySide from
>>> >>> > source?
>>> >>> >
>>> >>> > I get the following error when I run cmake inside the PySide/build
>>> >>> > dir.
>>> >>> > .........]$ cmake ..
>>> >>> > -- The C compiler identification is GNU 4.4.4
>>> >>> > -- The CXX compiler identification is GNU 4.4.4
>>> >>> > -- Check for working C compiler: /usr/bin/gcc
>>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>> >>> > -- Detecting C compiler ABI info
>>> >>> > -- Detecting C compiler ABI info - done
>>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>> >>> > -- Detecting CXX compiler ABI info
>>> >>> > -- Detecting CXX compiler ABI info - done
>>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>>> >>> >   By not providing "FindGeneratorRunner.cmake" in CMAKE_MODULE_PATH
>>> >>> > this
>>> >>> >   project has asked CMake to find a package configuration file
>>> >>> > provided
>>> >>> > by
>>> >>> >   "GeneratorRunner", but CMake did not find one.
>>> >>> >
>>> >>> >   Could not find a package configuration file provided by
>>> >>> > "GeneratorRunner"
>>> >>> >   (requested version 0.6.16) with any of the following names:
>>> >>> >
>>> >>> >     GeneratorRunnerConfig.cmake
>>> >>> >     generatorrunner-config.cmake
>>> >>> >
>>> >>> >   Add the installation prefix of "GeneratorRunner" to
>>> >>> > CMAKE_PREFIX_PATH
>>> >>> > or
>>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>>> >>> > above
>>> >>> > files.
>>> >>> >   If "GeneratorRunner" provides a separate development package or
>>> >>> > SDK,
>>> >>> > be
>>> >>> >   sure it has been installed.
>>> >>> >
>>> >>> >
>>> >>> > -- Configuring incomplete, errors occurred!
>>> >>> >
>>> >>> > Can anyone help on the proper build steps for building Pyside from
>>> >>> > Source?
>>> >>> >
>>> >>> > Regards,
>>> >>> > Tej
>>> >>> >
>>> >>> > _______________________________________________
>>> >>> > PySide mailing list
>>> >>> > PySide at qt-project.org
>>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>> >>> >
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > PySide mailing list
>>> > PySide at qt-project.org
>>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>> >
>>
>>


From tejashri.kandolkar at gmail.com  Tue Sep 11 13:42:34 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Tue, 11 Sep 2012 17:12:34 +0530
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
	<CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
Message-ID: <CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>

Hi,

A bit of confusion..could you please clarify?

PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT OK???

Regards,
Tej

On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>wrote:

> forgot to say that 64bit still does not build, just 32bit
>
> R.
>
> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
> > Hi Tej,
> >
> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >> Hi Roman,
> >>
> >> I was able to build PySide successfully on Windows 7 with Python 2.7.
> >> I now wanted to build it with Python 3.2..So wanted to know if the bug
> was
> >> fixed and if PySide can now be built with Python3.2?
> >
> > Yes, all known bugs were fixed and You can build even with latest Python
> 3.3rc2
> >
> >>
> >> Also, how do I check if I am getting the latest released PySide code?
> >> Is it that when I clone from github (without mentioning a version), it
> will
> >> always get the latest release?
> >>
> >
> > The setup.py build script has two parameters that control version of
> > PySide modules cloned from git: --list-versions and --version.
> >
> > For example to build latest stable version run:
> > python setup.py bdist --version=1.1.2 [...other params]
> >
> > To build latest development version run:
> > python setup.py bdist --version=1.1.3dev [...other params]
> >
> > To list all available versions run:
> > python setup.py --list-versions
> >
> > Regards
> > Roman
> >
> >> Regards,
> >> Tej
> >>
> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
> >> wrote:
> >>>
> >>> Hi Tej,
> >>>
> >>> the windows build will be available today or tomorrow, for python 2.7,
> >>> 3.2 and also 3.3rc
> >>>
> >>> Regards
> >>> Roman
> >>>
> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>> > Also, another question that I had was that is the build successful
> with
> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
> >>> >
> >>> > Regards,
> >>> > Tej
> >>> >
> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
> >>> > <tejashri.kandolkar at gmail.com> wrote:
> >>> >>
> >>> >> Hi,
> >>> >>
> >>> >> Thanks, I haven't tried building it again yet, but will be trying it
> >>> >> soon.
> >>> >> Also, can I have a rough idea of when the next release(with the
> >>> >> python3.2
> >>> >> related bug fixed) will be available?
> >>> >>
> >>> >> Because, ultimately I have to use Pyhon3.2.
> >>> >>
> >>> >> Regards,
> >>> >> Tej
> >>> >>
> >>> >>
> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko <
> backup.rlacko at gmail.com>
> >>> >> wrote:
> >>> >>>
> >>> >>> Hi,
> >>> >>>
> >>> >>> here is another option how to build PySide from source on Linux
> [1].
> >>> >>> There is known bug when building with python 3.2 that i will fix in
> >>> >>> next release.
> >>> >>>
> >>> >>> Regards
> >>> >>> R.
> >>> >>>
> >>> >>> [1]
> >>> >>>
> >>> >>>
> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
> >>> >>>
> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>> >>> > Hi,
> >>> >>> >
> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
> >>> >>> > I followed the steps mentioned @
> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
> >>> >>> > build
> >>> >>> > issues.
> >>> >>> >
> >>> >>> > I got the source code for the same from
> >>> >>> > http://qt-project.org/wiki/PySideDownloads
> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
> >>> >>> > generatorrunner directories are inside the Shiboken dir)
> >>> >>> >
> >>> >>> > Just want to make sure if thats the correct way to build PySide
> from
> >>> >>> > source?
> >>> >>> >
> >>> >>> > I get the following error when I run cmake inside the
> PySide/build
> >>> >>> > dir.
> >>> >>> > .........]$ cmake ..
> >>> >>> > -- The C compiler identification is GNU 4.4.4
> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
> >>> >>> > -- Detecting C compiler ABI info
> >>> >>> > -- Detecting C compiler ABI info - done
> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> >>> >>> > -- Detecting CXX compiler ABI info
> >>> >>> > -- Detecting CXX compiler ABI info - done
> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
> CMAKE_MODULE_PATH
> >>> >>> > this
> >>> >>> >   project has asked CMake to find a package configuration file
> >>> >>> > provided
> >>> >>> > by
> >>> >>> >   "GeneratorRunner", but CMake did not find one.
> >>> >>> >
> >>> >>> >   Could not find a package configuration file provided by
> >>> >>> > "GeneratorRunner"
> >>> >>> >   (requested version 0.6.16) with any of the following names:
> >>> >>> >
> >>> >>> >     GeneratorRunnerConfig.cmake
> >>> >>> >     generatorrunner-config.cmake
> >>> >>> >
> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
> >>> >>> > CMAKE_PREFIX_PATH
> >>> >>> > or
> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
> >>> >>> > above
> >>> >>> > files.
> >>> >>> >   If "GeneratorRunner" provides a separate development package or
> >>> >>> > SDK,
> >>> >>> > be
> >>> >>> >   sure it has been installed.
> >>> >>> >
> >>> >>> >
> >>> >>> > -- Configuring incomplete, errors occurred!
> >>> >>> >
> >>> >>> > Can anyone help on the proper build steps for building Pyside
> from
> >>> >>> > Source?
> >>> >>> >
> >>> >>> > Regards,
> >>> >>> > Tej
> >>> >>> >
> >>> >>> > _______________________________________________
> >>> >>> > PySide mailing list
> >>> >>> > PySide at qt-project.org
> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
> >>> >>> >
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > PySide mailing list
> >>> > PySide at qt-project.org
> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
> >>> >
> >>
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120911/37d315b6/attachment.html>

From backup.rlacko at gmail.com  Tue Sep 11 14:00:50 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 11 Sep 2012 14:00:50 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
	<CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
	<CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>
Message-ID: <CAHC6v6jaEYMCmyPN6DcSDyd+iQBy3cUo7R9gKeitqzqVUuZM3A@mail.gmail.com>

Hi,

PySide 1.1.2 is NOT buildable only against Qt4.8 64bit on windows.

PySide 1.1.2 against Qt4.8 64bit on linux is OK.
PySide 1.1.2 against Qt4.8 32bit on windows and linux is OK.
PySide 1.1.2 against Qt4.7 64bit on windows and linux is OK.
PySide 1.1.2 against Qt4.7 32bit on windows and linux is OK.

Regards
R.

2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi,
>
> A bit of confusion..could you please clarify?
>
> PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
> PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT OK???
>
> Regards,
> Tej
>
> On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>
> wrote:
>>
>> forgot to say that 64bit still does not build, just 32bit
>>
>> R.
>>
>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>> > Hi Tej,
>> >
>> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> >> Hi Roman,
>> >>
>> >> I was able to build PySide successfully on Windows 7 with Python 2.7.
>> >> I now wanted to build it with Python 3.2..So wanted to know if the bug
>> >> was
>> >> fixed and if PySide can now be built with Python3.2?
>> >
>> > Yes, all known bugs were fixed and You can build even with latest Python
>> > 3.3rc2
>> >
>> >>
>> >> Also, how do I check if I am getting the latest released PySide code?
>> >> Is it that when I clone from github (without mentioning a version), it
>> >> will
>> >> always get the latest release?
>> >>
>> >
>> > The setup.py build script has two parameters that control version of
>> > PySide modules cloned from git: --list-versions and --version.
>> >
>> > For example to build latest stable version run:
>> > python setup.py bdist --version=1.1.2 [...other params]
>> >
>> > To build latest development version run:
>> > python setup.py bdist --version=1.1.3dev [...other params]
>> >
>> > To list all available versions run:
>> > python setup.py --list-versions
>> >
>> > Regards
>> > Roman
>> >
>> >> Regards,
>> >> Tej
>> >>
>> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi Tej,
>> >>>
>> >>> the windows build will be available today or tomorrow, for python 2.7,
>> >>> 3.2 and also 3.3rc
>> >>>
>> >>> Regards
>> >>> Roman
>> >>>
>> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> >>> > Also, another question that I had was that is the build successful
>> >>> > with
>> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>> >>> >
>> >>> > Regards,
>> >>> > Tej
>> >>> >
>> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>> >>> > <tejashri.kandolkar at gmail.com> wrote:
>> >>> >>
>> >>> >> Hi,
>> >>> >>
>> >>> >> Thanks, I haven't tried building it again yet, but will be trying
>> >>> >> it
>> >>> >> soon.
>> >>> >> Also, can I have a rough idea of when the next release(with the
>> >>> >> python3.2
>> >>> >> related bug fixed) will be available?
>> >>> >>
>> >>> >> Because, ultimately I have to use Pyhon3.2.
>> >>> >>
>> >>> >> Regards,
>> >>> >> Tej
>> >>> >>
>> >>> >>
>> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko
>> >>> >> <backup.rlacko at gmail.com>
>> >>> >> wrote:
>> >>> >>>
>> >>> >>> Hi,
>> >>> >>>
>> >>> >>> here is another option how to build PySide from source on Linux
>> >>> >>> [1].
>> >>> >>> There is known bug when building with python 3.2 that i will fix
>> >>> >>> in
>> >>> >>> next release.
>> >>> >>>
>> >>> >>> Regards
>> >>> >>> R.
>> >>> >>>
>> >>> >>> [1]
>> >>> >>>
>> >>> >>>
>> >>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>> >>> >>>
>> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> >>> >>> > Hi,
>> >>> >>> >
>> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>> >>> >>> > I followed the steps mentioned @
>> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>> >>> >>> > build
>> >>> >>> > issues.
>> >>> >>> >
>> >>> >>> > I got the source code for the same from
>> >>> >>> > http://qt-project.org/wiki/PySideDownloads
>> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>> >>> >>> > generatorrunner directories are inside the Shiboken dir)
>> >>> >>> >
>> >>> >>> > Just want to make sure if thats the correct way to build PySide
>> >>> >>> > from
>> >>> >>> > source?
>> >>> >>> >
>> >>> >>> > I get the following error when I run cmake inside the
>> >>> >>> > PySide/build
>> >>> >>> > dir.
>> >>> >>> > .........]$ cmake ..
>> >>> >>> > -- The C compiler identification is GNU 4.4.4
>> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>> >>> >>> > -- Detecting C compiler ABI info
>> >>> >>> > -- Detecting C compiler ABI info - done
>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>> >>> >>> > -- Detecting CXX compiler ABI info
>> >>> >>> > -- Detecting CXX compiler ABI info - done
>> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
>> >>> >>> > CMAKE_MODULE_PATH
>> >>> >>> > this
>> >>> >>> >   project has asked CMake to find a package configuration file
>> >>> >>> > provided
>> >>> >>> > by
>> >>> >>> >   "GeneratorRunner", but CMake did not find one.
>> >>> >>> >
>> >>> >>> >   Could not find a package configuration file provided by
>> >>> >>> > "GeneratorRunner"
>> >>> >>> >   (requested version 0.6.16) with any of the following names:
>> >>> >>> >
>> >>> >>> >     GeneratorRunnerConfig.cmake
>> >>> >>> >     generatorrunner-config.cmake
>> >>> >>> >
>> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
>> >>> >>> > CMAKE_PREFIX_PATH
>> >>> >>> > or
>> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>> >>> >>> > above
>> >>> >>> > files.
>> >>> >>> >   If "GeneratorRunner" provides a separate development package
>> >>> >>> > or
>> >>> >>> > SDK,
>> >>> >>> > be
>> >>> >>> >   sure it has been installed.
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > -- Configuring incomplete, errors occurred!
>> >>> >>> >
>> >>> >>> > Can anyone help on the proper build steps for building Pyside
>> >>> >>> > from
>> >>> >>> > Source?
>> >>> >>> >
>> >>> >>> > Regards,
>> >>> >>> > Tej
>> >>> >>> >
>> >>> >>> > _______________________________________________
>> >>> >>> > PySide mailing list
>> >>> >>> > PySide at qt-project.org
>> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>> >>> >>> >
>> >>> >>
>> >>> >>
>> >>> >
>> >>> >
>> >>> > _______________________________________________
>> >>> > PySide mailing list
>> >>> > PySide at qt-project.org
>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>> >>> >
>> >>
>> >>
>
>


From backup.rlacko at gmail.com  Tue Sep 11 14:03:15 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 11 Sep 2012 14:03:15 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6jaEYMCmyPN6DcSDyd+iQBy3cUo7R9gKeitqzqVUuZM3A@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
	<CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
	<CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>
	<CAHC6v6jaEYMCmyPN6DcSDyd+iQBy3cUo7R9gKeitqzqVUuZM3A@mail.gmail.com>
Message-ID: <CAHC6v6jvZMnomhST7DSDGxgx=C6DLTDp=UO=N96v6Teawz9_wA@mail.gmail.com>

> PySide 1.1.2 is NOT buildable only against Qt4.8 64bit on windows.

and it fails to build agains all versions of python, not just 3.2

>
> PySide 1.1.2 against Qt4.8 64bit on linux is OK.
> PySide 1.1.2 against Qt4.8 32bit on windows and linux is OK.
> PySide 1.1.2 against Qt4.7 64bit on windows and linux is OK.
> PySide 1.1.2 against Qt4.7 32bit on windows and linux is OK.
>
> Regards
> R.
>
> 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> Hi,
>>
>> A bit of confusion..could you please clarify?
>>
>> PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
>> PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT OK???
>>
>> Regards,
>> Tej
>>
>> On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>
>> wrote:
>>>
>>> forgot to say that 64bit still does not build, just 32bit
>>>
>>> R.
>>>
>>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>> > Hi Tej,
>>> >
>>> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> >> Hi Roman,
>>> >>
>>> >> I was able to build PySide successfully on Windows 7 with Python 2.7.
>>> >> I now wanted to build it with Python 3.2..So wanted to know if the bug
>>> >> was
>>> >> fixed and if PySide can now be built with Python3.2?
>>> >
>>> > Yes, all known bugs were fixed and You can build even with latest Python
>>> > 3.3rc2
>>> >
>>> >>
>>> >> Also, how do I check if I am getting the latest released PySide code?
>>> >> Is it that when I clone from github (without mentioning a version), it
>>> >> will
>>> >> always get the latest release?
>>> >>
>>> >
>>> > The setup.py build script has two parameters that control version of
>>> > PySide modules cloned from git: --list-versions and --version.
>>> >
>>> > For example to build latest stable version run:
>>> > python setup.py bdist --version=1.1.2 [...other params]
>>> >
>>> > To build latest development version run:
>>> > python setup.py bdist --version=1.1.3dev [...other params]
>>> >
>>> > To list all available versions run:
>>> > python setup.py --list-versions
>>> >
>>> > Regards
>>> > Roman
>>> >
>>> >> Regards,
>>> >> Tej
>>> >>
>>> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
>>> >> wrote:
>>> >>>
>>> >>> Hi Tej,
>>> >>>
>>> >>> the windows build will be available today or tomorrow, for python 2.7,
>>> >>> 3.2 and also 3.3rc
>>> >>>
>>> >>> Regards
>>> >>> Roman
>>> >>>
>>> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> >>> > Also, another question that I had was that is the build successful
>>> >>> > with
>>> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>>> >>> >
>>> >>> > Regards,
>>> >>> > Tej
>>> >>> >
>>> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>>> >>> > <tejashri.kandolkar at gmail.com> wrote:
>>> >>> >>
>>> >>> >> Hi,
>>> >>> >>
>>> >>> >> Thanks, I haven't tried building it again yet, but will be trying
>>> >>> >> it
>>> >>> >> soon.
>>> >>> >> Also, can I have a rough idea of when the next release(with the
>>> >>> >> python3.2
>>> >>> >> related bug fixed) will be available?
>>> >>> >>
>>> >>> >> Because, ultimately I have to use Pyhon3.2.
>>> >>> >>
>>> >>> >> Regards,
>>> >>> >> Tej
>>> >>> >>
>>> >>> >>
>>> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko
>>> >>> >> <backup.rlacko at gmail.com>
>>> >>> >> wrote:
>>> >>> >>>
>>> >>> >>> Hi,
>>> >>> >>>
>>> >>> >>> here is another option how to build PySide from source on Linux
>>> >>> >>> [1].
>>> >>> >>> There is known bug when building with python 3.2 that i will fix
>>> >>> >>> in
>>> >>> >>> next release.
>>> >>> >>>
>>> >>> >>> Regards
>>> >>> >>> R.
>>> >>> >>>
>>> >>> >>> [1]
>>> >>> >>>
>>> >>> >>>
>>> >>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>> >>> >>>
>>> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> >>> >>> > Hi,
>>> >>> >>> >
>>> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>>> >>> >>> > I followed the steps mentioned @
>>> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>>> >>> >>> > build
>>> >>> >>> > issues.
>>> >>> >>> >
>>> >>> >>> > I got the source code for the same from
>>> >>> >>> > http://qt-project.org/wiki/PySideDownloads
>>> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>>> >>> >>> > generatorrunner directories are inside the Shiboken dir)
>>> >>> >>> >
>>> >>> >>> > Just want to make sure if thats the correct way to build PySide
>>> >>> >>> > from
>>> >>> >>> > source?
>>> >>> >>> >
>>> >>> >>> > I get the following error when I run cmake inside the
>>> >>> >>> > PySide/build
>>> >>> >>> > dir.
>>> >>> >>> > .........]$ cmake ..
>>> >>> >>> > -- The C compiler identification is GNU 4.4.4
>>> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>> >>> >>> > -- Detecting C compiler ABI info
>>> >>> >>> > -- Detecting C compiler ABI info - done
>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>> >>> >>> > -- Detecting CXX compiler ABI info
>>> >>> >>> > -- Detecting CXX compiler ABI info - done
>>> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>>> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
>>> >>> >>> > CMAKE_MODULE_PATH
>>> >>> >>> > this
>>> >>> >>> >   project has asked CMake to find a package configuration file
>>> >>> >>> > provided
>>> >>> >>> > by
>>> >>> >>> >   "GeneratorRunner", but CMake did not find one.
>>> >>> >>> >
>>> >>> >>> >   Could not find a package configuration file provided by
>>> >>> >>> > "GeneratorRunner"
>>> >>> >>> >   (requested version 0.6.16) with any of the following names:
>>> >>> >>> >
>>> >>> >>> >     GeneratorRunnerConfig.cmake
>>> >>> >>> >     generatorrunner-config.cmake
>>> >>> >>> >
>>> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
>>> >>> >>> > CMAKE_PREFIX_PATH
>>> >>> >>> > or
>>> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>>> >>> >>> > above
>>> >>> >>> > files.
>>> >>> >>> >   If "GeneratorRunner" provides a separate development package
>>> >>> >>> > or
>>> >>> >>> > SDK,
>>> >>> >>> > be
>>> >>> >>> >   sure it has been installed.
>>> >>> >>> >
>>> >>> >>> >
>>> >>> >>> > -- Configuring incomplete, errors occurred!
>>> >>> >>> >
>>> >>> >>> > Can anyone help on the proper build steps for building Pyside
>>> >>> >>> > from
>>> >>> >>> > Source?
>>> >>> >>> >
>>> >>> >>> > Regards,
>>> >>> >>> > Tej
>>> >>> >>> >
>>> >>> >>> > _______________________________________________
>>> >>> >>> > PySide mailing list
>>> >>> >>> > PySide at qt-project.org
>>> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>> >>> >>> >
>>> >>> >>
>>> >>> >>
>>> >>> >
>>> >>> >
>>> >>> > _______________________________________________
>>> >>> > PySide mailing list
>>> >>> > PySide at qt-project.org
>>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>> >>> >
>>> >>
>>> >>
>>
>>


From vihorev at gmail.com  Tue Sep 11 14:07:51 2012
From: vihorev at gmail.com (Alexey Vihorev)
Date: Tue, 11 Sep 2012 15:07:51 +0300
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6jvZMnomhST7DSDGxgx=C6DLTDp=UO=N96v6Teawz9_wA@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
	<CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
	<CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>
	<CAHC6v6jaEYMCmyPN6DcSDyd+iQBy3cUo7R9gKeitqzqVUuZM3A@mail.gmail.com>
	<CAHC6v6jvZMnomhST7DSDGxgx=C6DLTDp=UO=N96v6Teawz9_wA@mail.gmail.com>
Message-ID: <CAOrSsCbb-JUS42ZU6XXOJGdP9MYRihRxd4EZfnyxQbiM=KY3Lg@mail.gmail.com>

Is there any hope that it will eventually be fixed, or the situation
has to be considered as permanent?

2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>> PySide 1.1.2 is NOT buildable only against Qt4.8 64bit on windows.
>
> and it fails to build agains all versions of python, not just 3.2
>
>>
>> PySide 1.1.2 against Qt4.8 64bit on linux is OK.
>> PySide 1.1.2 against Qt4.8 32bit on windows and linux is OK.
>> PySide 1.1.2 against Qt4.7 64bit on windows and linux is OK.
>> PySide 1.1.2 against Qt4.7 32bit on windows and linux is OK.
>>
>> Regards
>> R.
>>
>> 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>> Hi,
>>>
>>> A bit of confusion..could you please clarify?
>>>
>>> PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
>>> PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT OK???
>>>
>>> Regards,
>>> Tej
>>>
>>> On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>
>>> wrote:
>>>>
>>>> forgot to say that 64bit still does not build, just 32bit
>>>>
>>>> R.
>>>>
>>>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>>> > Hi Tej,
>>>> >
>>>> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>> >> Hi Roman,
>>>> >>
>>>> >> I was able to build PySide successfully on Windows 7 with Python 2.7.
>>>> >> I now wanted to build it with Python 3.2..So wanted to know if the bug
>>>> >> was
>>>> >> fixed and if PySide can now be built with Python3.2?
>>>> >
>>>> > Yes, all known bugs were fixed and You can build even with latest Python
>>>> > 3.3rc2
>>>> >
>>>> >>
>>>> >> Also, how do I check if I am getting the latest released PySide code?
>>>> >> Is it that when I clone from github (without mentioning a version), it
>>>> >> will
>>>> >> always get the latest release?
>>>> >>
>>>> >
>>>> > The setup.py build script has two parameters that control version of
>>>> > PySide modules cloned from git: --list-versions and --version.
>>>> >
>>>> > For example to build latest stable version run:
>>>> > python setup.py bdist --version=1.1.2 [...other params]
>>>> >
>>>> > To build latest development version run:
>>>> > python setup.py bdist --version=1.1.3dev [...other params]
>>>> >
>>>> > To list all available versions run:
>>>> > python setup.py --list-versions
>>>> >
>>>> > Regards
>>>> > Roman
>>>> >
>>>> >> Regards,
>>>> >> Tej
>>>> >>
>>>> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
>>>> >> wrote:
>>>> >>>
>>>> >>> Hi Tej,
>>>> >>>
>>>> >>> the windows build will be available today or tomorrow, for python 2.7,
>>>> >>> 3.2 and also 3.3rc
>>>> >>>
>>>> >>> Regards
>>>> >>> Roman
>>>> >>>
>>>> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>> >>> > Also, another question that I had was that is the build successful
>>>> >>> > with
>>>> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>>>> >>> >
>>>> >>> > Regards,
>>>> >>> > Tej
>>>> >>> >
>>>> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>>>> >>> > <tejashri.kandolkar at gmail.com> wrote:
>>>> >>> >>
>>>> >>> >> Hi,
>>>> >>> >>
>>>> >>> >> Thanks, I haven't tried building it again yet, but will be trying
>>>> >>> >> it
>>>> >>> >> soon.
>>>> >>> >> Also, can I have a rough idea of when the next release(with the
>>>> >>> >> python3.2
>>>> >>> >> related bug fixed) will be available?
>>>> >>> >>
>>>> >>> >> Because, ultimately I have to use Pyhon3.2.
>>>> >>> >>
>>>> >>> >> Regards,
>>>> >>> >> Tej
>>>> >>> >>
>>>> >>> >>
>>>> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko
>>>> >>> >> <backup.rlacko at gmail.com>
>>>> >>> >> wrote:
>>>> >>> >>>
>>>> >>> >>> Hi,
>>>> >>> >>>
>>>> >>> >>> here is another option how to build PySide from source on Linux
>>>> >>> >>> [1].
>>>> >>> >>> There is known bug when building with python 3.2 that i will fix
>>>> >>> >>> in
>>>> >>> >>> next release.
>>>> >>> >>>
>>>> >>> >>> Regards
>>>> >>> >>> R.
>>>> >>> >>>
>>>> >>> >>> [1]
>>>> >>> >>>
>>>> >>> >>>
>>>> >>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>>> >>> >>>
>>>> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>> >>> >>> > Hi,
>>>> >>> >>> >
>>>> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>>>> >>> >>> > I followed the steps mentioned @
>>>> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>>>> >>> >>> > build
>>>> >>> >>> > issues.
>>>> >>> >>> >
>>>> >>> >>> > I got the source code for the same from
>>>> >>> >>> > http://qt-project.org/wiki/PySideDownloads
>>>> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>>>> >>> >>> > generatorrunner directories are inside the Shiboken dir)
>>>> >>> >>> >
>>>> >>> >>> > Just want to make sure if thats the correct way to build PySide
>>>> >>> >>> > from
>>>> >>> >>> > source?
>>>> >>> >>> >
>>>> >>> >>> > I get the following error when I run cmake inside the
>>>> >>> >>> > PySide/build
>>>> >>> >>> > dir.
>>>> >>> >>> > .........]$ cmake ..
>>>> >>> >>> > -- The C compiler identification is GNU 4.4.4
>>>> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>>> >>> >>> > -- Detecting C compiler ABI info
>>>> >>> >>> > -- Detecting C compiler ABI info - done
>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>>> >>> >>> > -- Detecting CXX compiler ABI info
>>>> >>> >>> > -- Detecting CXX compiler ABI info - done
>>>> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>>>> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
>>>> >>> >>> > CMAKE_MODULE_PATH
>>>> >>> >>> > this
>>>> >>> >>> >   project has asked CMake to find a package configuration file
>>>> >>> >>> > provided
>>>> >>> >>> > by
>>>> >>> >>> >   "GeneratorRunner", but CMake did not find one.
>>>> >>> >>> >
>>>> >>> >>> >   Could not find a package configuration file provided by
>>>> >>> >>> > "GeneratorRunner"
>>>> >>> >>> >   (requested version 0.6.16) with any of the following names:
>>>> >>> >>> >
>>>> >>> >>> >     GeneratorRunnerConfig.cmake
>>>> >>> >>> >     generatorrunner-config.cmake
>>>> >>> >>> >
>>>> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
>>>> >>> >>> > CMAKE_PREFIX_PATH
>>>> >>> >>> > or
>>>> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>>>> >>> >>> > above
>>>> >>> >>> > files.
>>>> >>> >>> >   If "GeneratorRunner" provides a separate development package
>>>> >>> >>> > or
>>>> >>> >>> > SDK,
>>>> >>> >>> > be
>>>> >>> >>> >   sure it has been installed.
>>>> >>> >>> >
>>>> >>> >>> >
>>>> >>> >>> > -- Configuring incomplete, errors occurred!
>>>> >>> >>> >
>>>> >>> >>> > Can anyone help on the proper build steps for building Pyside
>>>> >>> >>> > from
>>>> >>> >>> > Source?
>>>> >>> >>> >
>>>> >>> >>> > Regards,
>>>> >>> >>> > Tej
>>>> >>> >>> >
>>>> >>> >>> > _______________________________________________
>>>> >>> >>> > PySide mailing list
>>>> >>> >>> > PySide at qt-project.org
>>>> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>>> >>> >>> >
>>>> >>> >>
>>>> >>> >>
>>>> >>> >
>>>> >>> >
>>>> >>> > _______________________________________________
>>>> >>> > PySide mailing list
>>>> >>> > PySide at qt-project.org
>>>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>>> >>> >
>>>> >>
>>>> >>
>>>
>>>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside



-- 
Алексей Вихорев


From backup.rlacko at gmail.com  Tue Sep 11 14:36:20 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 11 Sep 2012 14:36:20 +0200
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAOrSsCbb-JUS42ZU6XXOJGdP9MYRihRxd4EZfnyxQbiM=KY3Lg@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
	<CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
	<CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>
	<CAHC6v6jaEYMCmyPN6DcSDyd+iQBy3cUo7R9gKeitqzqVUuZM3A@mail.gmail.com>
	<CAHC6v6jvZMnomhST7DSDGxgx=C6DLTDp=UO=N96v6Teawz9_wA@mail.gmail.com>
	<CAOrSsCbb-JUS42ZU6XXOJGdP9MYRihRxd4EZfnyxQbiM=KY3Lg@mail.gmail.com>
Message-ID: <CAHC6v6gsA-TzNpW5=mFrR=4ADkmHZddJPj5iSEdOXs=9Fjvi2A@mail.gmail.com>

Hi,

2012/9/11 Alexey Vihorev <vihorev at gmail.com>:
> Is there any hope that it will eventually be fixed, or the situation
> has to be considered as permanent?

It should be fixed ASAP, and it would be great if some great windows
developer helps here :)
Thanks
R.

>
> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>> PySide 1.1.2 is NOT buildable only against Qt4.8 64bit on windows.
>>
>> and it fails to build agains all versions of python, not just 3.2
>>
>>>
>>> PySide 1.1.2 against Qt4.8 64bit on linux is OK.
>>> PySide 1.1.2 against Qt4.8 32bit on windows and linux is OK.
>>> PySide 1.1.2 against Qt4.7 64bit on windows and linux is OK.
>>> PySide 1.1.2 against Qt4.7 32bit on windows and linux is OK.
>>>
>>> Regards
>>> R.
>>>
>>> 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>> Hi,
>>>>
>>>> A bit of confusion..could you please clarify?
>>>>
>>>> PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
>>>> PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT OK???
>>>>
>>>> Regards,
>>>> Tej
>>>>
>>>> On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>
>>>> wrote:
>>>>>
>>>>> forgot to say that 64bit still does not build, just 32bit
>>>>>
>>>>> R.
>>>>>
>>>>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>>>> > Hi Tej,
>>>>> >
>>>>> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>> >> Hi Roman,
>>>>> >>
>>>>> >> I was able to build PySide successfully on Windows 7 with Python 2.7.
>>>>> >> I now wanted to build it with Python 3.2..So wanted to know if the bug
>>>>> >> was
>>>>> >> fixed and if PySide can now be built with Python3.2?
>>>>> >
>>>>> > Yes, all known bugs were fixed and You can build even with latest Python
>>>>> > 3.3rc2
>>>>> >
>>>>> >>
>>>>> >> Also, how do I check if I am getting the latest released PySide code?
>>>>> >> Is it that when I clone from github (without mentioning a version), it
>>>>> >> will
>>>>> >> always get the latest release?
>>>>> >>
>>>>> >
>>>>> > The setup.py build script has two parameters that control version of
>>>>> > PySide modules cloned from git: --list-versions and --version.
>>>>> >
>>>>> > For example to build latest stable version run:
>>>>> > python setup.py bdist --version=1.1.2 [...other params]
>>>>> >
>>>>> > To build latest development version run:
>>>>> > python setup.py bdist --version=1.1.3dev [...other params]
>>>>> >
>>>>> > To list all available versions run:
>>>>> > python setup.py --list-versions
>>>>> >
>>>>> > Regards
>>>>> > Roman
>>>>> >
>>>>> >> Regards,
>>>>> >> Tej
>>>>> >>
>>>>> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
>>>>> >> wrote:
>>>>> >>>
>>>>> >>> Hi Tej,
>>>>> >>>
>>>>> >>> the windows build will be available today or tomorrow, for python 2.7,
>>>>> >>> 3.2 and also 3.3rc
>>>>> >>>
>>>>> >>> Regards
>>>>> >>> Roman
>>>>> >>>
>>>>> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>> >>> > Also, another question that I had was that is the build successful
>>>>> >>> > with
>>>>> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>>>>> >>> >
>>>>> >>> > Regards,
>>>>> >>> > Tej
>>>>> >>> >
>>>>> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>>>>> >>> > <tejashri.kandolkar at gmail.com> wrote:
>>>>> >>> >>
>>>>> >>> >> Hi,
>>>>> >>> >>
>>>>> >>> >> Thanks, I haven't tried building it again yet, but will be trying
>>>>> >>> >> it
>>>>> >>> >> soon.
>>>>> >>> >> Also, can I have a rough idea of when the next release(with the
>>>>> >>> >> python3.2
>>>>> >>> >> related bug fixed) will be available?
>>>>> >>> >>
>>>>> >>> >> Because, ultimately I have to use Pyhon3.2.
>>>>> >>> >>
>>>>> >>> >> Regards,
>>>>> >>> >> Tej
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko
>>>>> >>> >> <backup.rlacko at gmail.com>
>>>>> >>> >> wrote:
>>>>> >>> >>>
>>>>> >>> >>> Hi,
>>>>> >>> >>>
>>>>> >>> >>> here is another option how to build PySide from source on Linux
>>>>> >>> >>> [1].
>>>>> >>> >>> There is known bug when building with python 3.2 that i will fix
>>>>> >>> >>> in
>>>>> >>> >>> next release.
>>>>> >>> >>>
>>>>> >>> >>> Regards
>>>>> >>> >>> R.
>>>>> >>> >>>
>>>>> >>> >>> [1]
>>>>> >>> >>>
>>>>> >>> >>>
>>>>> >>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>>>> >>> >>>
>>>>> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>> >>> >>> > Hi,
>>>>> >>> >>> >
>>>>> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>>>>> >>> >>> > I followed the steps mentioned @
>>>>> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>>>>> >>> >>> > build
>>>>> >>> >>> > issues.
>>>>> >>> >>> >
>>>>> >>> >>> > I got the source code for the same from
>>>>> >>> >>> > http://qt-project.org/wiki/PySideDownloads
>>>>> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>>>>> >>> >>> > generatorrunner directories are inside the Shiboken dir)
>>>>> >>> >>> >
>>>>> >>> >>> > Just want to make sure if thats the correct way to build PySide
>>>>> >>> >>> > from
>>>>> >>> >>> > source?
>>>>> >>> >>> >
>>>>> >>> >>> > I get the following error when I run cmake inside the
>>>>> >>> >>> > PySide/build
>>>>> >>> >>> > dir.
>>>>> >>> >>> > .........]$ cmake ..
>>>>> >>> >>> > -- The C compiler identification is GNU 4.4.4
>>>>> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
>>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
>>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>>>> >>> >>> > -- Detecting C compiler ABI info
>>>>> >>> >>> > -- Detecting C compiler ABI info - done
>>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>>>> >>> >>> > -- Detecting CXX compiler ABI info
>>>>> >>> >>> > -- Detecting CXX compiler ABI info - done
>>>>> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>>>>> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
>>>>> >>> >>> > CMAKE_MODULE_PATH
>>>>> >>> >>> > this
>>>>> >>> >>> >   project has asked CMake to find a package configuration file
>>>>> >>> >>> > provided
>>>>> >>> >>> > by
>>>>> >>> >>> >   "GeneratorRunner", but CMake did not find one.
>>>>> >>> >>> >
>>>>> >>> >>> >   Could not find a package configuration file provided by
>>>>> >>> >>> > "GeneratorRunner"
>>>>> >>> >>> >   (requested version 0.6.16) with any of the following names:
>>>>> >>> >>> >
>>>>> >>> >>> >     GeneratorRunnerConfig.cmake
>>>>> >>> >>> >     generatorrunner-config.cmake
>>>>> >>> >>> >
>>>>> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
>>>>> >>> >>> > CMAKE_PREFIX_PATH
>>>>> >>> >>> > or
>>>>> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>>>>> >>> >>> > above
>>>>> >>> >>> > files.
>>>>> >>> >>> >   If "GeneratorRunner" provides a separate development package
>>>>> >>> >>> > or
>>>>> >>> >>> > SDK,
>>>>> >>> >>> > be
>>>>> >>> >>> >   sure it has been installed.
>>>>> >>> >>> >
>>>>> >>> >>> >
>>>>> >>> >>> > -- Configuring incomplete, errors occurred!
>>>>> >>> >>> >
>>>>> >>> >>> > Can anyone help on the proper build steps for building Pyside
>>>>> >>> >>> > from
>>>>> >>> >>> > Source?
>>>>> >>> >>> >
>>>>> >>> >>> > Regards,
>>>>> >>> >>> > Tej
>>>>> >>> >>> >
>>>>> >>> >>> > _______________________________________________
>>>>> >>> >>> > PySide mailing list
>>>>> >>> >>> > PySide at qt-project.org
>>>>> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>>>> >>> >>> >
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >
>>>>> >>> >
>>>>> >>> > _______________________________________________
>>>>> >>> > PySide mailing list
>>>>> >>> > PySide at qt-project.org
>>>>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>>>> >>> >
>>>>> >>
>>>>> >>
>>>>
>>>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
>
> --
> Алексей Вихорев


From felix.morency at gmail.com  Tue Sep 11 14:38:25 2012
From: felix.morency at gmail.com (=?UTF-8?Q?F=C3=A9lix_C=2E_Morency?=)
Date: Tue, 11 Sep 2012 08:38:25 -0400
Subject: [PySide] Problem since update to 1.1.2 Ubuntu
Message-ID: <CAG=jP7jXwQ9AKDE2B-qe4NVGPigv=GywWsxL3uFy4m=AjOOUJQ@mail.gmail.com>

Hi all,

I updated to 1.1.2 using the Ubuntu PySide PPA this morning and I have
to following error when launching my application:

Traceback (most recent call last):
  File "run_player.py", line 8, in <module>
    from PySide.QtCore import *
ImportError: /usr/lib/python2.7/dist-packages/PySide/QtCore.so:
undefined symbol: _ZN8Shiboken6Object4hashEP7_object

It was working well with 1.1.1. Any idea what is going on?

Regards,
--
Félix C. Morency, M.Sc.
Plateforme d’analyse et de visualisation d’images
Centre Hospitalier Universitaire de Sherbrooke
Centre de recherche clinique Étienne-Le Bel
Local Z5-3031 | 819.346.1110 ext 16634


From Zhu.Zhong at alcatel-sbell.com.cn  Tue Sep 11 14:39:26 2012
From: Zhu.Zhong at alcatel-sbell.com.cn (ZHONG Zhu)
Date: Tue, 11 Sep 2012 12:39:26 +0000
Subject: [PySide] where to find doc for Shiboken
In-Reply-To: <CAG=jP7jXwQ9AKDE2B-qe4NVGPigv=GywWsxL3uFy4m=AjOOUJQ@mail.gmail.com>
References: <CAG=jP7jXwQ9AKDE2B-qe4NVGPigv=GywWsxL3uFy4m=AjOOUJQ@mail.gmail.com>
Message-ID: <E2C879D9F3A55B44BF5818CEE6D385D9130710@CNSHJMBX02.ad4.ad.alcatel.com>

Hi all,

Do you know where to find user guide for Shiboken?

Thanks,

Zhu

From vihorev at gmail.com  Tue Sep 11 14:42:26 2012
From: vihorev at gmail.com (Alexey Vihorev)
Date: Tue, 11 Sep 2012 15:42:26 +0300
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6gsA-TzNpW5=mFrR=4ADkmHZddJPj5iSEdOXs=9Fjvi2A@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAHC6v6g3OJz_xPxJBv5GS7b5qHcn+uiOkyk6_KJ_Ffdnaja-QQ@mail.gmail.com>
	<CAMKcwJv+=O+hjNeM-aY_dPc-aHwF=jAjPi23XwhpHYZO+fj+RQ@mail.gmail.com>
	<CAMKcwJvx7zc00BxYnwqnrSv0P0ykA6eP3KrypYS+0JeOyEXd8Q@mail.gmail.com>
	<CAHC6v6g00R8NQgPpj0H4xFhTmN36s6ctXQ91jeLuCD0c48ynCA@mail.gmail.com>
	<CAMKcwJsJ_PTDREzvQotn5fuEnjFJU4OqF24uyH5riLQH-FwmzA@mail.gmail.com>
	<CAHC6v6jXbO1WdhbKG5nJAU7UfPMHsrk8Bp_pnaJjRD+e_tW=9w@mail.gmail.com>
	<CAHC6v6gy+nSRSn3QNMCu+zE8C1BDVuEv2aB1u1NmZ=CAnXcyWQ@mail.gmail.com>
	<CAMKcwJs9Zq=Vg+dKK3tEaLBe-fT7SNSZGf68KOYJFJ_b6p2=8A@mail.gmail.com>
	<CAHC6v6jaEYMCmyPN6DcSDyd+iQBy3cUo7R9gKeitqzqVUuZM3A@mail.gmail.com>
	<CAHC6v6jvZMnomhST7DSDGxgx=C6DLTDp=UO=N96v6Teawz9_wA@mail.gmail.com>
	<CAOrSsCbb-JUS42ZU6XXOJGdP9MYRihRxd4EZfnyxQbiM=KY3Lg@mail.gmail.com>
	<CAHC6v6gsA-TzNpW5=mFrR=4ADkmHZddJPj5iSEdOXs=9Fjvi2A@mail.gmail.com>
Message-ID: <CAOrSsCaByhmTgwg05Z0aD5Zqt9nTpzgiTFNYo=Kb3fdUi+C_9A@mail.gmail.com>

I would be glad to contribute, but my knowledge of C++ and a build
processes/scripts is lacking, to put it mildly. I'm just a novice
Python developer. Sorry...

2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
> Hi,
>
> 2012/9/11 Alexey Vihorev <vihorev at gmail.com>:
>> Is there any hope that it will eventually be fixed, or the situation
>> has to be considered as permanent?
>
> It should be fixed ASAP, and it would be great if some great windows
> developer helps here :)
> Thanks
> R.
>
>>
>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>>> PySide 1.1.2 is NOT buildable only against Qt4.8 64bit on windows.
>>>
>>> and it fails to build agains all versions of python, not just 3.2
>>>
>>>>
>>>> PySide 1.1.2 against Qt4.8 64bit on linux is OK.
>>>> PySide 1.1.2 against Qt4.8 32bit on windows and linux is OK.
>>>> PySide 1.1.2 against Qt4.7 64bit on windows and linux is OK.
>>>> PySide 1.1.2 against Qt4.7 32bit on windows and linux is OK.
>>>>
>>>> Regards
>>>> R.
>>>>
>>>> 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>> Hi,
>>>>>
>>>>> A bit of confusion..could you please clarify?
>>>>>
>>>>> PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
>>>>> PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT OK???
>>>>>
>>>>> Regards,
>>>>> Tej
>>>>>
>>>>> On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> forgot to say that 64bit still does not build, just 32bit
>>>>>>
>>>>>> R.
>>>>>>
>>>>>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>>>>> > Hi Tej,
>>>>>> >
>>>>>> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>>> >> Hi Roman,
>>>>>> >>
>>>>>> >> I was able to build PySide successfully on Windows 7 with Python 2.7.
>>>>>> >> I now wanted to build it with Python 3.2..So wanted to know if the bug
>>>>>> >> was
>>>>>> >> fixed and if PySide can now be built with Python3.2?
>>>>>> >
>>>>>> > Yes, all known bugs were fixed and You can build even with latest Python
>>>>>> > 3.3rc2
>>>>>> >
>>>>>> >>
>>>>>> >> Also, how do I check if I am getting the latest released PySide code?
>>>>>> >> Is it that when I clone from github (without mentioning a version), it
>>>>>> >> will
>>>>>> >> always get the latest release?
>>>>>> >>
>>>>>> >
>>>>>> > The setup.py build script has two parameters that control version of
>>>>>> > PySide modules cloned from git: --list-versions and --version.
>>>>>> >
>>>>>> > For example to build latest stable version run:
>>>>>> > python setup.py bdist --version=1.1.2 [...other params]
>>>>>> >
>>>>>> > To build latest development version run:
>>>>>> > python setup.py bdist --version=1.1.3dev [...other params]
>>>>>> >
>>>>>> > To list all available versions run:
>>>>>> > python setup.py --list-versions
>>>>>> >
>>>>>> > Regards
>>>>>> > Roman
>>>>>> >
>>>>>> >> Regards,
>>>>>> >> Tej
>>>>>> >>
>>>>>> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko <backup.rlacko at gmail.com>
>>>>>> >> wrote:
>>>>>> >>>
>>>>>> >>> Hi Tej,
>>>>>> >>>
>>>>>> >>> the windows build will be available today or tomorrow, for python 2.7,
>>>>>> >>> 3.2 and also 3.3rc
>>>>>> >>>
>>>>>> >>> Regards
>>>>>> >>> Roman
>>>>>> >>>
>>>>>> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>>> >>> > Also, another question that I had was that is the build successful
>>>>>> >>> > with
>>>>>> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
>>>>>> >>> >
>>>>>> >>> > Regards,
>>>>>> >>> > Tej
>>>>>> >>> >
>>>>>> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
>>>>>> >>> > <tejashri.kandolkar at gmail.com> wrote:
>>>>>> >>> >>
>>>>>> >>> >> Hi,
>>>>>> >>> >>
>>>>>> >>> >> Thanks, I haven't tried building it again yet, but will be trying
>>>>>> >>> >> it
>>>>>> >>> >> soon.
>>>>>> >>> >> Also, can I have a rough idea of when the next release(with the
>>>>>> >>> >> python3.2
>>>>>> >>> >> related bug fixed) will be available?
>>>>>> >>> >>
>>>>>> >>> >> Because, ultimately I have to use Pyhon3.2.
>>>>>> >>> >>
>>>>>> >>> >> Regards,
>>>>>> >>> >> Tej
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko
>>>>>> >>> >> <backup.rlacko at gmail.com>
>>>>>> >>> >> wrote:
>>>>>> >>> >>>
>>>>>> >>> >>> Hi,
>>>>>> >>> >>>
>>>>>> >>> >>> here is another option how to build PySide from source on Linux
>>>>>> >>> >>> [1].
>>>>>> >>> >>> There is known bug when building with python 3.2 that i will fix
>>>>>> >>> >>> in
>>>>>> >>> >>> next release.
>>>>>> >>> >>>
>>>>>> >>> >>> Regards
>>>>>> >>> >>> R.
>>>>>> >>> >>>
>>>>>> >>> >>> [1]
>>>>>> >>> >>>
>>>>>> >>> >>>
>>>>>> >>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
>>>>>> >>> >>>
>>>>>> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>>>>>> >>> >>> > Hi,
>>>>>> >>> >>> >
>>>>>> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
>>>>>> >>> >>> > I followed the steps mentioned @
>>>>>> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i face
>>>>>> >>> >>> > build
>>>>>> >>> >>> > issues.
>>>>>> >>> >>> >
>>>>>> >>> >>> > I got the source code for the same from
>>>>>> >>> >>> > http://qt-project.org/wiki/PySideDownloads
>>>>>> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor and
>>>>>> >>> >>> > generatorrunner directories are inside the Shiboken dir)
>>>>>> >>> >>> >
>>>>>> >>> >>> > Just want to make sure if thats the correct way to build PySide
>>>>>> >>> >>> > from
>>>>>> >>> >>> > source?
>>>>>> >>> >>> >
>>>>>> >>> >>> > I get the following error when I run cmake inside the
>>>>>> >>> >>> > PySide/build
>>>>>> >>> >>> > dir.
>>>>>> >>> >>> > .........]$ cmake ..
>>>>>> >>> >>> > -- The C compiler identification is GNU 4.4.4
>>>>>> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
>>>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
>>>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>>>>> >>> >>> > -- Detecting C compiler ABI info
>>>>>> >>> >>> > -- Detecting C compiler ABI info - done
>>>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
>>>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>>>>> >>> >>> > -- Detecting CXX compiler ABI info
>>>>>> >>> >>> > -- Detecting CXX compiler ABI info - done
>>>>>> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
>>>>>> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
>>>>>> >>> >>> > CMAKE_MODULE_PATH
>>>>>> >>> >>> > this
>>>>>> >>> >>> >   project has asked CMake to find a package configuration file
>>>>>> >>> >>> > provided
>>>>>> >>> >>> > by
>>>>>> >>> >>> >   "GeneratorRunner", but CMake did not find one.
>>>>>> >>> >>> >
>>>>>> >>> >>> >   Could not find a package configuration file provided by
>>>>>> >>> >>> > "GeneratorRunner"
>>>>>> >>> >>> >   (requested version 0.6.16) with any of the following names:
>>>>>> >>> >>> >
>>>>>> >>> >>> >     GeneratorRunnerConfig.cmake
>>>>>> >>> >>> >     generatorrunner-config.cmake
>>>>>> >>> >>> >
>>>>>> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
>>>>>> >>> >>> > CMAKE_PREFIX_PATH
>>>>>> >>> >>> > or
>>>>>> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of the
>>>>>> >>> >>> > above
>>>>>> >>> >>> > files.
>>>>>> >>> >>> >   If "GeneratorRunner" provides a separate development package
>>>>>> >>> >>> > or
>>>>>> >>> >>> > SDK,
>>>>>> >>> >>> > be
>>>>>> >>> >>> >   sure it has been installed.
>>>>>> >>> >>> >
>>>>>> >>> >>> >
>>>>>> >>> >>> > -- Configuring incomplete, errors occurred!
>>>>>> >>> >>> >
>>>>>> >>> >>> > Can anyone help on the proper build steps for building Pyside
>>>>>> >>> >>> > from
>>>>>> >>> >>> > Source?
>>>>>> >>> >>> >
>>>>>> >>> >>> > Regards,
>>>>>> >>> >>> > Tej
>>>>>> >>> >>> >
>>>>>> >>> >>> > _______________________________________________
>>>>>> >>> >>> > PySide mailing list
>>>>>> >>> >>> > PySide at qt-project.org
>>>>>> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>> >>> >>> >
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> >>> >
>>>>>> >>> >
>>>>>> >>> > _______________________________________________
>>>>>> >>> > PySide mailing list
>>>>>> >>> > PySide at qt-project.org
>>>>>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>> >>> >
>>>>>> >>
>>>>>> >>
>>>>>
>>>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>>
>> --
>> Алексей Вихорев



-- 
Алексей Вихорев


From backup.rlacko at gmail.com  Tue Sep 11 14:54:44 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 11 Sep 2012 14:54:44 +0200
Subject: [PySide] PySide 1.1.2 Windows builds available
Message-ID: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>

Hi,

PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
3.2 and 3.3rc2.

Packages and installation instruction are available here:
http://qt-project.org/wiki/PySide_Binaries_Windows

Regards
Roman


From hugo.lima at openbossa.org  Tue Sep 11 15:36:25 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Tue, 11 Sep 2012 10:36:25 -0300
Subject: [PySide] Wrong PyObject reference counting leads to memory leak
	in QMap->PyDict converter template code of
	PySide/QtCore/typesystem_core_common.xml
In-Reply-To: <CAGrH=yrv6eV7UGNv57Nv4f_e_bUgQPrB9501nbsAzqb-hX0NUg@mail.gmail.com>
References: <CAGrH=yrv6eV7UGNv57Nv4f_e_bUgQPrB9501nbsAzqb-hX0NUg@mail.gmail.com>
Message-ID: <1721735.ArJD5nneVW@hugodesktop>

On Monday, September 10, 2012 08:34:23 PM Dennis Victorovich wrote:
> Hi everyone.
> 
> While migrating our project from PySide v1.0.9 to v1.1.1 we've spotted a
> memory leak. (no leak with older 1.0.9 apiextractor and shiboken)
> 
> We've found and fixed small problem in conversion code in
> PySide/QtCore/typesystem_core_common.xml.
> 
> We've checked our fix on ubuntu 32/64 and Win32 builds.
> Problem is fixed, no memory leak.
> 
> Bug is reported https://bugreports.qt-project.org/browse/PYSIDE-107
> Patch is attached.
> Hope this will help.

Patch integrated, thanks very much!
 
> Best regards.
> Dennis Shilko.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120911/b282fae8/attachment.sig>

From hugo.lima at openbossa.org  Tue Sep 11 15:46:33 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Tue, 11 Sep 2012 10:46:33 -0300
Subject: [PySide] Unable build PySide from Source on Linux
In-Reply-To: <CAHC6v6gsA-TzNpW5=mFrR=4ADkmHZddJPj5iSEdOXs=9Fjvi2A@mail.gmail.com>
References: <CAMKcwJuDc8xHvx3qX5RaT8MnW7WFFXbKpW-_e-QdofVBGnVsdA@mail.gmail.com>
	<CAOrSsCbb-JUS42ZU6XXOJGdP9MYRihRxd4EZfnyxQbiM=KY3Lg@mail.gmail.com>
	<CAHC6v6gsA-TzNpW5=mFrR=4ADkmHZddJPj5iSEdOXs=9Fjvi2A@mail.gmail.com>
Message-ID: <16041089.gttnF1rD0Z@hugodesktop>

On Tuesday, September 11, 2012 02:36:20 PM Roman Lacko wrote:
> Hi,
> 
> 2012/9/11 Alexey Vihorev <vihorev at gmail.com>:
> > Is there any hope that it will eventually be fixed, or the situation
> > has to be considered as permanent?
> 
> It should be fixed ASAP, and it would be great if some great windows
> developer helps here :)
> Thanks
> R.

For sure it's not permanent, but as Roman said, we need Windows developers to 
help us with patches.
 
> > 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
> >>> PySide 1.1.2 is NOT buildable only against Qt4.8 64bit on windows.
> >> 
> >> and it fails to build agains all versions of python, not just 3.2
> >> 
> >>> PySide 1.1.2 against Qt4.8 64bit on linux is OK.
> >>> PySide 1.1.2 against Qt4.8 32bit on windows and linux is OK.
> >>> PySide 1.1.2 against Qt4.7 64bit on windows and linux is OK.
> >>> PySide 1.1.2 against Qt4.7 32bit on windows and linux is OK.
> >>> 
> >>> Regards
> >>> R.
> >>> 
> >>> 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>>> Hi,
> >>>> 
> >>>> A bit of confusion..could you please clarify?
> >>>> 
> >>>> PySide1.1.2 + Python2.7 + Qt4.7.4 on 64-bit(both Win and Linux) is OK
> >>>> PySide1.1.2 + Python3.2 + Qt4.7.4 on 64-bit(both Win and Linux) is NOT
> >>>> OK???
> >>>> 
> >>>> Regards,
> >>>> Tej
> >>>> 
> >>>> On Tue, Sep 11, 2012 at 4:53 PM, Roman Lacko <backup.rlacko at gmail.com>
> >>>> 
> >>>> wrote:
> >>>>> forgot to say that 64bit still does not build, just 32bit
> >>>>> 
> >>>>> R.
> >>>>> 
> >>>>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
> >>>>> > Hi Tej,
> >>>>> > 
> >>>>> > 2012/9/11 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>>>> >> Hi Roman,
> >>>>> >> 
> >>>>> >> I was able to build PySide successfully on Windows 7 with Python
> >>>>> >> 2.7.
> >>>>> >> I now wanted to build it with Python 3.2..So wanted to know if the
> >>>>> >> bug
> >>>>> >> was
> >>>>> >> fixed and if PySide can now be built with Python3.2?
> >>>>> > 
> >>>>> > Yes, all known bugs were fixed and You can build even with latest
> >>>>> > Python
> >>>>> > 3.3rc2
> >>>>> > 
> >>>>> >> Also, how do I check if I am getting the latest released PySide
> >>>>> >> code?
> >>>>> >> Is it that when I clone from github (without mentioning a version),
> >>>>> >> it
> >>>>> >> will
> >>>>> >> always get the latest release?
> >>>>> > 
> >>>>> > The setup.py build script has two parameters that control version of
> >>>>> > PySide modules cloned from git: --list-versions and --version.
> >>>>> > 
> >>>>> > For example to build latest stable version run:
> >>>>> > python setup.py bdist --version=1.1.2 [...other params]
> >>>>> > 
> >>>>> > To build latest development version run:
> >>>>> > python setup.py bdist --version=1.1.3dev [...other params]
> >>>>> > 
> >>>>> > To list all available versions run:
> >>>>> > python setup.py --list-versions
> >>>>> > 
> >>>>> > Regards
> >>>>> > Roman
> >>>>> > 
> >>>>> >> Regards,
> >>>>> >> Tej
> >>>>> >> 
> >>>>> >> On Mon, Sep 10, 2012 at 12:16 PM, Roman Lacko
> >>>>> >> <backup.rlacko at gmail.com>
> >>>>> >> 
> >>>>> >> wrote:
> >>>>> >>> Hi Tej,
> >>>>> >>> 
> >>>>> >>> the windows build will be available today or tomorrow, for python
> >>>>> >>> 2.7,
> >>>>> >>> 3.2 and also 3.3rc
> >>>>> >>> 
> >>>>> >>> Regards
> >>>>> >>> Roman
> >>>>> >>> 
> >>>>> >>> 2012/9/10 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>>>> >>> > Also, another question that I had was that is the build
> >>>>> >>> > successful
> >>>>> >>> > with
> >>>>> >>> > Python 3.1 (on Win7 32/64 and Linux 64bit?)
> >>>>> >>> > 
> >>>>> >>> > Regards,
> >>>>> >>> > Tej
> >>>>> >>> > 
> >>>>> >>> > On Mon, Sep 10, 2012 at 12:11 PM, Tejashri Kandolkar
> >>>>> >>> > 
> >>>>> >>> > <tejashri.kandolkar at gmail.com> wrote:
> >>>>> >>> >> Hi,
> >>>>> >>> >> 
> >>>>> >>> >> Thanks, I haven't tried building it again yet, but will be
> >>>>> >>> >> trying
> >>>>> >>> >> it
> >>>>> >>> >> soon.
> >>>>> >>> >> Also, can I have a rough idea of when the next release(with the
> >>>>> >>> >> python3.2
> >>>>> >>> >> related bug fixed) will be available?
> >>>>> >>> >> 
> >>>>> >>> >> Because, ultimately I have to use Pyhon3.2.
> >>>>> >>> >> 
> >>>>> >>> >> Regards,
> >>>>> >>> >> Tej
> >>>>> >>> >> 
> >>>>> >>> >> 
> >>>>> >>> >> On Thu, Sep 6, 2012 at 11:56 AM, Roman Lacko
> >>>>> >>> >> <backup.rlacko at gmail.com>
> >>>>> >>> >> 
> >>>>> >>> >> wrote:
> >>>>> >>> >>> Hi,
> >>>>> >>> >>> 
> >>>>> >>> >>> here is another option how to build PySide from source on
> >>>>> >>> >>> Linux
> >>>>> >>> >>> [1].
> >>>>> >>> >>> There is known bug when building with python 3.2 that i will
> >>>>> >>> >>> fix
> >>>>> >>> >>> in
> >>>>> >>> >>> next release.
> >>>>> >>> >>> 
> >>>>> >>> >>> Regards
> >>>>> >>> >>> R.
> >>>>> >>> >>> 
> >>>>> >>> >>> [1]
> >>>>> >>> >>> 
> >>>>> >>> >>> 
> >>>>> >>> >>> http://pypi.python.org/pypi/PySide#installing-pyside-from-sour
> >>>>> >>> >>> ce-on-a-unix-system-ubuntu-12-04-lts>>>>> >>> >>> 
> >>>>> >>> >>> 2012/9/6 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> >>>>> >>> >>> > Hi,
> >>>>> >>> >>> > 
> >>>>> >>> >>> > I am trying to build Pyside on Linux RHEL 64-bit machine.
> >>>>> >>> >>> > I followed the steps mentioned @
> >>>>> >>> >>> > http://qt-project.org/wiki/Building_PySide_on_Linux, but i
> >>>>> >>> >>> > face
> >>>>> >>> >>> > build
> >>>>> >>> >>> > issues.
> >>>>> >>> >>> > 
> >>>>> >>> >>> > I got the source code for the same from
> >>>>> >>> >>> > http://qt-project.org/wiki/PySideDownloads
> >>>>> >>> >>> > and I only find PySide and Shiboken tar files (ApiExtractor
> >>>>> >>> >>> > and
> >>>>> >>> >>> > generatorrunner directories are inside the Shiboken dir)
> >>>>> >>> >>> > 
> >>>>> >>> >>> > Just want to make sure if thats the correct way to build
> >>>>> >>> >>> > PySide
> >>>>> >>> >>> > from
> >>>>> >>> >>> > source?
> >>>>> >>> >>> > 
> >>>>> >>> >>> > I get the following error when I run cmake inside the
> >>>>> >>> >>> > PySide/build
> >>>>> >>> >>> > dir.
> >>>>> >>> >>> > .........]$ cmake ..
> >>>>> >>> >>> > -- The C compiler identification is GNU 4.4.4
> >>>>> >>> >>> > -- The CXX compiler identification is GNU 4.4.4
> >>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc
> >>>>> >>> >>> > -- Check for working C compiler: /usr/bin/gcc -- works
> >>>>> >>> >>> > -- Detecting C compiler ABI info
> >>>>> >>> >>> > -- Detecting C compiler ABI info - done
> >>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++
> >>>>> >>> >>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> >>>>> >>> >>> > -- Detecting CXX compiler ABI info
> >>>>> >>> >>> > -- Detecting CXX compiler ABI info - done
> >>>>> >>> >>> > 
> >>>>> >>> >>> > CMake Error at CMakeLists.txt:8 (find_package):
> >>>>> >>> >>> >   By not providing "FindGeneratorRunner.cmake" in
> >>>>> >>> >>> > 
> >>>>> >>> >>> > CMAKE_MODULE_PATH
> >>>>> >>> >>> > this
> >>>>> >>> >>> > 
> >>>>> >>> >>> >   project has asked CMake to find a package configuration
> >>>>> >>> >>> >   file
> >>>>> >>> >>> > 
> >>>>> >>> >>> > provided
> >>>>> >>> >>> > by
> >>>>> >>> >>> > 
> >>>>> >>> >>> >   "GeneratorRunner", but CMake did not find one.
> >>>>> >>> >>> >   
> >>>>> >>> >>> >   Could not find a package configuration file provided by
> >>>>> >>> >>> > 
> >>>>> >>> >>> > "GeneratorRunner"
> >>>>> >>> >>> > 
> >>>>> >>> >>> >   (requested version 0.6.16) with any of the following 
names:
> >>>>> >>> >>> >     GeneratorRunnerConfig.cmake
> >>>>> >>> >>> >     generatorrunner-config.cmake
> >>>>> >>> >>> >   
> >>>>> >>> >>> >   Add the installation prefix of "GeneratorRunner" to
> >>>>> >>> >>> > 
> >>>>> >>> >>> > CMAKE_PREFIX_PATH
> >>>>> >>> >>> > or
> >>>>> >>> >>> > 
> >>>>> >>> >>> >   set "GeneratorRunner_DIR" to a directory containing one of
> >>>>> >>> >>> >   the
> >>>>> >>> >>> > 
> >>>>> >>> >>> > above
> >>>>> >>> >>> > files.
> >>>>> >>> >>> > 
> >>>>> >>> >>> >   If "GeneratorRunner" provides a separate development
> >>>>> >>> >>> >   package
> >>>>> >>> >>> > 
> >>>>> >>> >>> > or
> >>>>> >>> >>> > SDK,
> >>>>> >>> >>> > be
> >>>>> >>> >>> > 
> >>>>> >>> >>> >   sure it has been installed.
> >>>>> >>> >>> > 
> >>>>> >>> >>> > -- Configuring incomplete, errors occurred!
> >>>>> >>> >>> > 
> >>>>> >>> >>> > Can anyone help on the proper build steps for building
> >>>>> >>> >>> > Pyside
> >>>>> >>> >>> > from
> >>>>> >>> >>> > Source?
> >>>>> >>> >>> > 
> >>>>> >>> >>> > Regards,
> >>>>> >>> >>> > Tej
> >>>>> >>> >>> > 
> >>>>> >>> >>> > _______________________________________________
> >>>>> >>> >>> > PySide mailing list
> >>>>> >>> >>> > PySide at qt-project.org
> >>>>> >>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
> >>>>> >>> > 
> >>>>> >>> > _______________________________________________
> >>>>> >>> > PySide mailing list
> >>>>> >>> > PySide at qt-project.org
> >>>>> >>> > http://lists.qt-project.org/mailman/listinfo/pyside
> >> 
> >> _______________________________________________
> >> PySide mailing list
> >> PySide at qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/pyside
> > 
> > --
> > Алексей Вихорев
> 
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120911/6e898736/attachment.sig>

From dev at projekt01.ch  Tue Sep 11 16:01:50 2012
From: dev at projekt01.ch (Roger)
Date: Tue, 11 Sep 2012 16:01:50 +0200
Subject: [PySide] PySide 1.1.2 Windows builds available
In-Reply-To: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
References: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
Message-ID: <00e101cd9025$ff728f60$fe57ae20$@projekt01.ch>

Thanks a lot, Roman

Regards
Roger Ineichen
_____________________________
END OF MESSAGE

> Betreff: [PySide] PySide 1.1.2 Windows builds available
> 
> Hi,
> 
> PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
> 3.2 and 3.3rc2.
> 
> Packages and installation instruction are available here:
> http://qt-project.org/wiki/PySide_Binaries_Windows
> 
> Regards
> Roman
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside




From sscc at mweb.co.za  Tue Sep 11 16:47:55 2012
From: sscc at mweb.co.za (Alex Strickland)
Date: Tue, 11 Sep 2012 16:47:55 +0200
Subject: [PySide] PySide 1.1.2 Windows builds available
In-Reply-To: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
References: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
Message-ID: <504F4F1B.3000201@mweb.co.za>

On 2012/09/11 02:54 PM, Roman Lacko wrote:

> PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
> 3.2 and 3.3rc2.

Thought I'd give it a quick whirl and boom - "Hello World" with Windows 
and Python 2.7.3. Thank you, now I need to *do* something with it!

-- 
Regards
Alex


From vihorev at gmail.com  Tue Sep 11 16:49:50 2012
From: vihorev at gmail.com (Alexey Vihorev)
Date: Tue, 11 Sep 2012 17:49:50 +0300
Subject: [PySide] PySide 1.1.2 Windows builds available
In-Reply-To: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
References: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
Message-ID: <CAOrSsCbuwzat5o7V-Hkc7Gp=tb2oaEy59+8nfeEpAn-_9dmhag@mail.gmail.com>

Great to hear and many thanks for your work!

2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
> Hi,
>
> PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
> 3.2 and 3.3rc2.
>
> Packages and installation instruction are available here:
> http://qt-project.org/wiki/PySide_Binaries_Windows
>
> Regards
> Roman
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside



-- 
Алексей Вихорев


From techabc at gmail.com  Tue Sep 11 16:53:53 2012
From: techabc at gmail.com (techabc)
Date: Tue, 11 Sep 2012 22:53:53 +0800
Subject: [PySide] PySide 1.1.2 Windows builds available
In-Reply-To: <CAOrSsCbuwzat5o7V-Hkc7Gp=tb2oaEy59+8nfeEpAn-_9dmhag@mail.gmail.com>
References: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
	<CAOrSsCbuwzat5o7V-Hkc7Gp=tb2oaEy59+8nfeEpAn-_9dmhag@mail.gmail.com>
Message-ID: <CAPPwZt7tKbry_pAFwqgERwahccGQvuiZU2O81K8H=F0ZH=wdsQ@mail.gmail.com>

can NOT run the demo:
D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo>python qtdemo.py
Traceback (most recent call last):
  File "qtdemo.py", line 51, in <module>
    import qtdemo_rc
  File "D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo\qtdemo_rc.py"
, line 3602, in <module>
    qInitResources()
  File "D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo\qtdemo_rc.py"
, line 3597, in qInitResources
    QtCore.qRegisterResourceData(0x01, qt_resource_struct, qt_resource_name, qt_
resource_data)
TypeError: 'qRegisterResourceData' called with wrong argument types:
  qRegisterResourceData(int, str, str, str)
Supported signatures:
  qRegisterResourceData(int, unicode, unicode, unicode)

D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo>


2012/9/11 Alexey Vihorev <vihorev at gmail.com>:
> Great to hear and many thanks for your work!
>
> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>> Hi,
>>
>> PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
>> 3.2 and 3.3rc2.
>>
>> Packages and installation instruction are available here:
>> http://qt-project.org/wiki/PySide_Binaries_Windows
>>
>> Regards
>> Roman
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
>
> --
> Алексей Вихорев
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From vladovi at atlas.cz  Tue Sep 11 20:04:59 2012
From: vladovi at atlas.cz (=?ISO-8859-2?Q?Vl=E1=EFa?=)
Date: Tue, 11 Sep 2012 20:04:59 +0200
Subject: [PySide] PySide 1.1.2 Windows builds available
In-Reply-To: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
References: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
Message-ID: <504F7D4B.1050402@atlas.cz>

Hi Roman,

thanks a lot for the new builds. Unfortunately I have a problem with 
displaying accented characters. Please check the 2 screenshots 
(http://oi46.tinypic.com/vzc7l0.jpg, 
http://oi46.tinypic.com/dmbo12.jpg). The first one is from version 
1.1.1, the second one from 1.1.2. Do you have any idea why the accented 
chracters are displayed incorrectly in the new version?

Thank you,
Vladimir

Dne 11.9.2012 14:54, Roman Lacko napsal(a):
> Hi,
>
> PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
> 3.2 and 3.3rc2.
>
> Packages and installation instruction are available here:
> http://qt-project.org/wiki/PySide_Binaries_Windows
>
> Regards
> Roman
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pyside_new.png
Type: image/png
Size: 37609 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120911/b4bf3a17/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pyside_old.png
Type: image/png
Size: 37917 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120911/b4bf3a17/attachment-0001.png>

From backup.rlacko at gmail.com  Wed Sep 12 09:24:19 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 12 Sep 2012 09:24:19 +0200
Subject: [PySide] PySide 1.1.2 Windows builds available
In-Reply-To: <CAPPwZt7tKbry_pAFwqgERwahccGQvuiZU2O81K8H=F0ZH=wdsQ@mail.gmail.com>
References: <CAHC6v6j4UpXju3LkD72iwWu+NOGAyjLUxq2JzAxTAApkNRS6pA@mail.gmail.com>
	<CAOrSsCbuwzat5o7V-Hkc7Gp=tb2oaEy59+8nfeEpAn-_9dmhag@mail.gmail.com>
	<CAPPwZt7tKbry_pAFwqgERwahccGQvuiZU2O81K8H=F0ZH=wdsQ@mail.gmail.com>
Message-ID: <CAHC6v6h=XGOGm3Ba6ctuKY_j1KGSb3NTK9jqPpop9dEcLDq=AQ@mail.gmail.com>

Hi,
You need to regenerate the qtdemo_rc.py with pyside-rcc tool with -py3
option (by default rcc generates code for python 2).

Please run the following command:

D:\Python32\Lib\site-packages\PySide\pyside-rcc.exe -py3
D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo\qtdemo.qrc
-o D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo\qtdemo_rc.py

Regards
Roman

2012/9/11 techabc <techabc at gmail.com>:
> can NOT run the demo:
> D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo>python qtdemo.py
> Traceback (most recent call last):
>   File "qtdemo.py", line 51, in <module>
>     import qtdemo_rc
>   File "D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo\qtdemo_rc.py"
> , line 3602, in <module>
>     qInitResources()
>   File "D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo\qtdemo_rc.py"
> , line 3597, in qInitResources
>     QtCore.qRegisterResourceData(0x01, qt_resource_struct, qt_resource_name, qt_
> resource_data)
> TypeError: 'qRegisterResourceData' called with wrong argument types:
>   qRegisterResourceData(int, str, str, str)
> Supported signatures:
>   qRegisterResourceData(int, unicode, unicode, unicode)
>
> D:\Python32\Lib\site-packages\PySide\examples\demos\qtdemo>
>
>
> 2012/9/11 Alexey Vihorev <vihorev at gmail.com>:
>> Great to hear and many thanks for your work!
>>
>> 2012/9/11 Roman Lacko <backup.rlacko at gmail.com>:
>>> Hi,
>>>
>>> PySide 1.1.2 windows builds are available for 32 bit Python 2.6, 2.7,
>>> 3.2 and 3.3rc2.
>>>
>>> Packages and installation instruction are available here:
>>> http://qt-project.org/wiki/PySide_Binaries_Windows
>>>
>>> Regards
>>> Roman
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>>
>> --
>> Алексей Вихорев
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From backup.rlacko at gmail.com  Wed Sep 12 12:20:28 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 12 Sep 2012 12:20:28 +0200
Subject: [PySide] strange QObject bahaviour on Python 3.2 (Windows and Linux)
Message-ID: <CAHC6v6g1Q5jTsA0XnEBVcEfO_ovGseSweDuTes71ni=HnTGGWA@mail.gmail.com>

Hi,

I have discovered strange bahaviour while testing qtdemo.py under Python 3.2.
Plase look at sample code and the comment prefixed XXX:

>>>
from PySide import QtCore

class MenuManager(QtCore.QObject):

    pInstance = None

    @classmethod
    def instance(cls):
        if cls.pInstance is None:
            cls_inst = cls()
            cls.pInstance = cls_inst
            # XXX: the cls.pInstance is None but cls_inst is NOT None !!!

        return cls.pInstance

# This will allways return None under Python 3.2
menuManagerInstance = MenuManager.instance()
print(menuManagerInstance)
<<<

Under Python 2.6 and 2.7 the code work as expected (cls.pInstance is NOT None)
If MenuManager inherits from object it will work (class
MenuManager(object)), so there is something wrong with QObject
wrapper...
Under PyQt4 it works fine.

I have absolutely no idea what is going on here.

Regards
Roman


From backup.rlacko at gmail.com  Wed Sep 12 12:49:11 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 12 Sep 2012 12:49:11 +0200
Subject: [PySide] strange QObject bahaviour on Python 3.2 (Windows and
	Linux)
In-Reply-To: <CAE-5t2vOGDsWo2D4ojvDEoCg5HPVW=Q+0A0dvFvrVpt89wok9w@mail.gmail.com>
References: <CAHC6v6g1Q5jTsA0XnEBVcEfO_ovGseSweDuTes71ni=HnTGGWA@mail.gmail.com>
	<CAE-5t2vOGDsWo2D4ojvDEoCg5HPVW=Q+0A0dvFvrVpt89wok9w@mail.gmail.com>
Message-ID: <CAHC6v6hSK+R3RFKKOYpyfUu0HCk04zRwTBQr3LW8E235_-kzCg@mail.gmail.com>

AFAIK "self" is not available on class methods (see @classmethod
modificator), cls should point to class object not to instance object

regards
R.

2012/9/12 Thomas Pietrowski <thopiekar at gmail.com>:
> Hey,
>
> I'm not familiar to Python3, but what happens, when you replace:
>
> def instance(cls):
>
> with:
>
> def instance(self, cls):
>
> For me it seems that it uses cls as self in that function, if self is not
> set in the function of your class.
> But, as I said, I'm not sure if that could be your solution ;-)
>
> Am 12.09.2012 12:20 schrieb "Roman Lacko" <backup.rlacko at gmail.com>:
>>
>> Hi,
>>
>> I have discovered strange bahaviour while testing qtdemo.py under Python
>> 3.2.
>> Plase look at sample code and the comment prefixed XXX:
>>
>> >>>
>> from PySide import QtCore
>>
>> class MenuManager(QtCore.QObject):
>>
>>     pInstance = None
>>
>>     @classmethod
>>     def instance(cls):
>>         if cls.pInstance is None:
>>             cls_inst = cls()
>>             cls.pInstance = cls_inst
>>             # XXX: the cls.pInstance is None but cls_inst is NOT None !!!
>>
>>         return cls.pInstance
>>
>> # This will allways return None under Python 3.2
>> menuManagerInstance = MenuManager.instance()
>> print(menuManagerInstance)
>> <<<
>>
>> Under Python 2.6 and 2.7 the code work as expected (cls.pInstance is NOT
>> None)
>> If MenuManager inherits from object it will work (class
>> MenuManager(object)), so there is something wrong with QObject
>> wrapper...
>> Under PyQt4 it works fine.
>>
>> I have absolutely no idea what is going on here.
>>
>> Regards
>> Roman
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside


From backup.rlacko at gmail.com  Wed Sep 12 13:41:32 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 12 Sep 2012 13:41:32 +0200
Subject: [PySide] strange QObject bahaviour on Python 3.2 (Windows and
	Linux)
In-Reply-To: <CAE-5t2vOGDsWo2D4ojvDEoCg5HPVW=Q+0A0dvFvrVpt89wok9w@mail.gmail.com>
References: <CAHC6v6g1Q5jTsA0XnEBVcEfO_ovGseSweDuTes71ni=HnTGGWA@mail.gmail.com>
	<CAE-5t2vOGDsWo2D4ojvDEoCg5HPVW=Q+0A0dvFvrVpt89wok9w@mail.gmail.com>
Message-ID: <CAHC6v6j2nqv3=QQ1PGjJ-pxOqsxUecKD0NsFnXS6xmJyT95a6A@mail.gmail.com>

here is more better example, see comments:

from PySide import QtCore
class MyObject(QtCore.QObject):
    Instance = "default value"

# This will print "new value"
MyObject.Instance = "new value"
print(MyObject.Instance)

# This will print "default value"
MyObject.Instance
MyObject.Instance = "new value"
print(MyObject.Instance)

When I access the MyObject.Instance, than the value of
MyObject.Instance is allways "default value" !

R.

2012/9/12 Thomas Pietrowski <thopiekar at gmail.com>:
> Hey,
>
> I'm not familiar to Python3, but what happens, when you replace:
>
> def instance(cls):
>
> with:
>
> def instance(self, cls):
>
> For me it seems that it uses cls as self in that function, if self is not
> set in the function of your class.
> But, as I said, I'm not sure if that could be your solution ;-)
>
> Am 12.09.2012 12:20 schrieb "Roman Lacko" <backup.rlacko at gmail.com>:
>>
>> Hi,
>>
>> I have discovered strange bahaviour while testing qtdemo.py under Python
>> 3.2.
>> Plase look at sample code and the comment prefixed XXX:
>>
>> >>>
>> from PySide import QtCore
>>
>> class MenuManager(QtCore.QObject):
>>
>>     pInstance = None
>>
>>     @classmethod
>>     def instance(cls):
>>         if cls.pInstance is None:
>>             cls_inst = cls()
>>             cls.pInstance = cls_inst
>>             # XXX: the cls.pInstance is None but cls_inst is NOT None !!!
>>
>>         return cls.pInstance
>>
>> # This will allways return None under Python 3.2
>> menuManagerInstance = MenuManager.instance()
>> print(menuManagerInstance)
>> <<<
>>
>> Under Python 2.6 and 2.7 the code work as expected (cls.pInstance is NOT
>> None)
>> If MenuManager inherits from object it will work (class
>> MenuManager(object)), so there is something wrong with QObject
>> wrapper...
>> Under PyQt4 it works fine.
>>
>> I have absolutely no idea what is going on here.
>>
>> Regards
>> Roman
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside


From backup.rlacko at gmail.com  Wed Sep 12 13:46:58 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Wed, 12 Sep 2012 13:46:58 +0200
Subject: [PySide] strange QObject bahaviour on Python 3.2 (Windows and
	Linux)
In-Reply-To: <CAHC6v6j2nqv3=QQ1PGjJ-pxOqsxUecKD0NsFnXS6xmJyT95a6A@mail.gmail.com>
References: <CAHC6v6g1Q5jTsA0XnEBVcEfO_ovGseSweDuTes71ni=HnTGGWA@mail.gmail.com>
	<CAE-5t2vOGDsWo2D4ojvDEoCg5HPVW=Q+0A0dvFvrVpt89wok9w@mail.gmail.com>
	<CAHC6v6j2nqv3=QQ1PGjJ-pxOqsxUecKD0NsFnXS6xmJyT95a6A@mail.gmail.com>
Message-ID: <CAHC6v6i1hMz=sZ0_OGxVmFKoEC6pS9RuFWKuD5fd7=5x8V1CwQ@mail.gmail.com>

...this looks like critical error, and we should fix it ASAP, until
then i don't recommend to use pyside 1.1.2 with python 3.2. Both
windows and linux versions are affected

2012/9/12 Roman Lacko <backup.rlacko at gmail.com>:
> here is more better example, see comments:
>
> from PySide import QtCore
> class MyObject(QtCore.QObject):
>     Instance = "default value"
>
> # This will print "new value"
> MyObject.Instance = "new value"
> print(MyObject.Instance)
>
> # This will print "default value"
> MyObject.Instance
> MyObject.Instance = "new value"
> print(MyObject.Instance)
>
> When I access the MyObject.Instance, than the value of
> MyObject.Instance is allways "default value" !
>
> R.
>
> 2012/9/12 Thomas Pietrowski <thopiekar at gmail.com>:
>> Hey,
>>
>> I'm not familiar to Python3, but what happens, when you replace:
>>
>> def instance(cls):
>>
>> with:
>>
>> def instance(self, cls):
>>
>> For me it seems that it uses cls as self in that function, if self is not
>> set in the function of your class.
>> But, as I said, I'm not sure if that could be your solution ;-)
>>
>> Am 12.09.2012 12:20 schrieb "Roman Lacko" <backup.rlacko at gmail.com>:
>>>
>>> Hi,
>>>
>>> I have discovered strange bahaviour while testing qtdemo.py under Python
>>> 3.2.
>>> Plase look at sample code and the comment prefixed XXX:
>>>
>>> >>>
>>> from PySide import QtCore
>>>
>>> class MenuManager(QtCore.QObject):
>>>
>>>     pInstance = None
>>>
>>>     @classmethod
>>>     def instance(cls):
>>>         if cls.pInstance is None:
>>>             cls_inst = cls()
>>>             cls.pInstance = cls_inst
>>>             # XXX: the cls.pInstance is None but cls_inst is NOT None !!!
>>>
>>>         return cls.pInstance
>>>
>>> # This will allways return None under Python 3.2
>>> menuManagerInstance = MenuManager.instance()
>>> print(menuManagerInstance)
>>> <<<
>>>
>>> Under Python 2.6 and 2.7 the code work as expected (cls.pInstance is NOT
>>> None)
>>> If MenuManager inherits from object it will work (class
>>> MenuManager(object)), so there is something wrong with QObject
>>> wrapper...
>>> Under PyQt4 it works fine.
>>>
>>> I have absolutely no idea what is going on here.
>>>
>>> Regards
>>> Roman
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside


From tejashri.kandolkar at gmail.com  Thu Sep 13 15:20:39 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Thu, 13 Sep 2012 18:50:39 +0530
Subject: [PySide] Cloning from git takes too long - Pyside build on Win7
Message-ID: <CAMKcwJs81it+v8PYJgkXg7Cqc9P3_dUSiqCV6Vic3qNBEB9XoQ@mail.gmail.com>

Hi,

I am trying to build PySide on Win7 by following instructions @
http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
I have built it before in the same way and it had worked fine for me.

But recently when I tried to build it, looks like cloning takes just way
too long, and at times its even hung.
Is anyone else facing such an issue? I am not able to build PySide because
of this issue.

Regards,
Tej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120913/63331a94/attachment.html>

From tejashri.kandolkar at gmail.com  Thu Sep 13 15:26:14 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Thu, 13 Sep 2012 18:56:14 +0530
Subject: [PySide] Cloning from git takes too long - Pyside build on Win7
In-Reply-To: <CAMKcwJs81it+v8PYJgkXg7Cqc9P3_dUSiqCV6Vic3qNBEB9XoQ@mail.gmail.com>
References: <CAMKcwJs81it+v8PYJgkXg7Cqc9P3_dUSiqCV6Vic3qNBEB9XoQ@mail.gmail.com>
Message-ID: <CAMKcwJuw6YYubAAYxyLPwcqNdoa1VV+Z5Ai+h9qYgZqTazhV6g@mail.gmail.com>

Also, I have noticed this happens while cloning mainly
'sources/pyside-examples'..

On Thu, Sep 13, 2012 at 6:50 PM, Tejashri Kandolkar <
tejashri.kandolkar at gmail.com> wrote:

> Hi,
>
> I am trying to build PySide on Win7 by following instructions @
> http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
> I have built it before in the same way and it had worked fine for me.
>
> But recently when I tried to build it, looks like cloning takes just way
> too long, and at times its even hung.
> Is anyone else facing such an issue? I am not able to build PySide because
> of this issue.
>
> Regards,
> Tej
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120913/3bd35b9d/attachment.html>

From backup.rlacko at gmail.com  Thu Sep 13 15:31:18 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Thu, 13 Sep 2012 15:31:18 +0200
Subject: [PySide] Cloning from git takes too long - Pyside build on Win7
In-Reply-To: <CAMKcwJs81it+v8PYJgkXg7Cqc9P3_dUSiqCV6Vic3qNBEB9XoQ@mail.gmail.com>
References: <CAMKcwJs81it+v8PYJgkXg7Cqc9P3_dUSiqCV6Vic3qNBEB9XoQ@mail.gmail.com>
Message-ID: <CAHC6v6iDubZHJRB7L0HZTAAXBTecUStBtjSSTka5j4vauym+pA@mail.gmail.com>

yes gitorious has some issues when cloning pyside-examples

But you dont need to clone anything, just download the source
distribution from PyPI, it contains full source code of all PySide
modules (pyside, shiboken, tools and examples).

The build script will automatically discover that this is not git
clone and will build the binaries offline

R.

2012/9/13 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi,
>
> I am trying to build PySide on Win7 by following instructions
> @http://pypi.python.org/pypi/PySide#installing-pyside-from-source-on-a-unix-system-ubuntu-12-04-lts
> I have built it before in the same way and it had worked fine for me.
>
> But recently when I tried to build it, looks like cloning takes just way too
> long, and at times its even hung.
> Is anyone else facing such an issue? I am not able to build PySide because
> of this issue.
>
> Regards,
> Tej
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From ameyadambir at gmail.com  Mon Sep 17 08:52:30 2012
From: ameyadambir at gmail.com (ameya dambir)
Date: Mon, 17 Sep 2012 12:22:30 +0530
Subject: [PySide] Fwd: problem while installing PySide
In-Reply-To: <CA+ec0Bo7_=WUgN+ti7M-gBGGpc=H_VwSfpAVfyvTkoH9FNaSmA@mail.gmail.com>
References: <CA+ec0Bo7_=WUgN+ti7M-gBGGpc=H_VwSfpAVfyvTkoH9FNaSmA@mail.gmail.com>
Message-ID: <CA+ec0BpN1TJFDmtp=gd-2CuUNRF+dhQ_JK3vUwAtPT2UfL3ijw@mail.gmail.com>

Hi,

I am trying to install PySide on RHEL machine. I am getting following error
while running setup.py file.

Traceback (most recent call last):
  File "/user/ameya/python_rel/bin/pyside_postinstall.py", line 84, in
install_linux
    from PySide import QtCore
ImportError:
/user/ameya/python_rel/lib/python3.2/site-packages/PySide/libpyside.cpython-32m.so.1.1:
undefined symbol: _Z9qBadAllocv
The PySide package not installed: None

On the above path that so file is present. This path is set into
LD_LIBRARY_PATH as well.

Take look at this as well
bash-3.2$ python
Python 3.2 (r32:88445, Sep 13 2012, 09:36:20)
[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import PySide
>>>

Is it successful import ??

On the other hand

>>> from PySide.QtCore import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError:
/user/ameya/python_rel/lib/python3.2/site-packages/PySide/libpyside.cpython-32m.so.1.1:
undefined symbol: _Z9qBadAllocv

Can anybody help?

Ameya.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120917/4535e328/attachment.html>

From backup.rlacko at gmail.com  Mon Sep 17 10:42:46 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Mon, 17 Sep 2012 10:42:46 +0200
Subject: [PySide] Fwd: problem while installing PySide
In-Reply-To: <CA+ec0BpN1TJFDmtp=gd-2CuUNRF+dhQ_JK3vUwAtPT2UfL3ijw@mail.gmail.com>
References: <CA+ec0Bo7_=WUgN+ti7M-gBGGpc=H_VwSfpAVfyvTkoH9FNaSmA@mail.gmail.com>
	<CA+ec0BpN1TJFDmtp=gd-2CuUNRF+dhQ_JK3vUwAtPT2UfL3ijw@mail.gmail.com>
Message-ID: <CAHC6v6hafHar6_E-kSouhsoQ7hH7v11OsC6Lxopd4JtzBq8U1g@mail.gmail.com>

Hi,

can you send me the full build output ?
it contains build configuration and setup details

Thanks
R.

2012/9/17 ameya dambir <ameyadambir at gmail.com>:
> Hi,
>
> I am trying to install PySide on RHEL machine. I am getting following error
> while running setup.py file.
>
> Traceback (most recent call last):
>   File "/user/ameya/python_rel/bin/pyside_postinstall.py", line 84, in
> install_linux
>     from PySide import QtCore
> ImportError:
> /user/ameya/python_rel/lib/python3.2/site-packages/PySide/libpyside.cpython-32m.so.1.1:
> undefined symbol: _Z9qBadAllocv
> The PySide package not installed: None
>
> On the above path that so file is present. This path is set into
> LD_LIBRARY_PATH as well.
>
> Take look at this as well
> bash-3.2$ python
> Python 3.2 (r32:88445, Sep 13 2012, 09:36:20)
> [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import PySide
>>>>
>
> Is it successful import ??
>
> On the other hand
>
>>>> from PySide.QtCore import *
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ImportError:
> /user/ameya/python_rel/lib/python3.2/site-packages/PySide/libpyside.cpython-32m.so.1.1:
> undefined symbol: _Z9qBadAllocv



>
> Can anybody help?
>
> Ameya.
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From backup.rlacko at gmail.com  Mon Sep 17 12:25:20 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Mon, 17 Sep 2012 12:25:20 +0200
Subject: [PySide] Fwd: problem while installing PySide
In-Reply-To: <CA+ec0BpoyuXKC2tSa7eZu79aZ=6ArTBfy6ZzhFp-+NtiVasyVA@mail.gmail.com>
References: <CA+ec0Bo7_=WUgN+ti7M-gBGGpc=H_VwSfpAVfyvTkoH9FNaSmA@mail.gmail.com>
	<CA+ec0BpN1TJFDmtp=gd-2CuUNRF+dhQ_JK3vUwAtPT2UfL3ijw@mail.gmail.com>
	<CAHC6v6hafHar6_E-kSouhsoQ7hH7v11OsC6Lxopd4JtzBq8U1g@mail.gmail.com>
	<CA+ec0BpoyuXKC2tSa7eZu79aZ=6ArTBfy6ZzhFp-+NtiVasyVA@mail.gmail.com>
Message-ID: <CAHC6v6gr01kgzFCtZW_4Ve82riHK-11V63k34wNK98W8whfYrg@mail.gmail.com>

Hi,
the problem is that you are building against Qt that is not in system path.

Please try one of the following fixes and let me know if it works:

1. add qt libs to path or to LD_LIBRARY_PATH - in your case the path
is /dev/ameya/qt/bin
OR
2. build the pyside with --standalone option. with this option setup
script will copy qt libs to PySide installation folder and makes the
PySide "standalone" and independent from qt installed in system
OR
3. add qt libs to PySide folder manually if you dont want to rebuild
whole PySide

I recommend to use option 2. using --stanalone setup.py parameter

Regards
R.

2012/9/17 ameya dambir <ameyadambir at gmail.com>:
> Hi Roman,
>
> I have attached build & error log with this mail.
> Please have a look.
>
> Thanks in advance.
>
> Ameya
>
> On 9/17/12, Roman Lacko <backup.rlacko at gmail.com> wrote:
>> Hi,
>>
>> can you send me the full build output ?
>> it contains build configuration and setup details
>>
>> Thanks
>> R.
>>
>> 2012/9/17 ameya dambir <ameyadambir at gmail.com>:
>>> Hi,
>>>
>>> I am trying to install PySide on RHEL machine. I am getting following
>>> error
>>> while running setup.py file.
>>>
>>> Traceback (most recent call last):
>>>   File "/user/ameya/python_rel/bin/pyside_postinstall.py", line 84, in
>>> install_linux
>>>     from PySide import QtCore
>>> ImportError:
>>> /user/ameya/python_rel/lib/python3.2/site-packages/PySide/libpyside.cpython-32m.so.1.1:
>>> undefined symbol: _Z9qBadAllocv
>>> The PySide package not installed: None
>>>
>>> On the above path that so file is present. This path is set into
>>> LD_LIBRARY_PATH as well.
>>>
>>> Take look at this as well
>>> bash-3.2$ python
>>> Python 3.2 (r32:88445, Sep 13 2012, 09:36:20)
>>> [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>>>> import PySide
>>>>>>
>>>
>>> Is it successful import ??
>>>
>>> On the other hand
>>>
>>>>>> from PySide.QtCore import *
>>> Traceback (most recent call last):
>>>   File "<stdin>", line 1, in <module>
>>> ImportError:
>>> /user/ameya/python_rel/lib/python3.2/site-packages/PySide/libpyside.cpython-32m.so.1.1:
>>> undefined symbol: _Z9qBadAllocv
>>
>>
>>
>>>
>>> Can anybody help?
>>>
>>> Ameya.
>>>
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>
>
>
> --
> hello


From tejashri.kandolkar at gmail.com  Mon Sep 17 13:38:18 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Mon, 17 Sep 2012 17:08:18 +0530
Subject: [PySide] Build problem on Windows7 32-bit - Could NOT find
 PythonInterp (missing: PYTHON_EXECUTABLE)
Message-ID: <CAMKcwJuhf_MD87960tJohYomURb64F3w25Wk9pJw3o3yCyEKzg@mail.gmail.com>

Hi,

I am building PySide from source on win7 32-bit using Python3.2.3,and I get
the following error:

-- Detecting CXX compiler ABI info - done
CMake Error at
c:/cmake28/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.
cmake:97 (MESSAGE):
  Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
Call Stack (most recent call first):

c:/cmake28/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:288
(_F
PHSA_FAILURE_MESSAGE)
  c:/cmake28/share/cmake-2.8/Modules/FindPythonInterp.cmake:139
(FIND_PACKAGE_HA
NDLE_STANDARD_ARGS)
  CMakeLists.txt:5 (find_package)


-- Configuring incomplete, errors occurred!
setup.py:411: ResourceWarning: unclosed file <_io.TextIOWrapper name=4
encoding=
'cp1252'>
  if run_process(cmake_cmd, log) != 0:
setup.py:411: ResourceWarning: unclosed file <_io.TextIOWrapper name=3
encoding=
'cp1252'>
  if run_process(cmake_cmd, log) != 0:
error: Error configuring pyside-tools


Why is CMake not able to find my python interpretor?
I have set my custom path of python3.2 bin in PATH env variable correctly.

(and the same builds fine on 64-bit machine)
Am I missing something here?

Regards,
Tej.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120917/b54a3f8e/attachment.html>

From backup.rlacko at gmail.com  Mon Sep 17 13:42:09 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Mon, 17 Sep 2012 13:42:09 +0200
Subject: [PySide] Build problem on Windows7 32-bit - Could NOT find
 PythonInterp (missing: PYTHON_EXECUTABLE)
In-Reply-To: <CAMKcwJuhf_MD87960tJohYomURb64F3w25Wk9pJw3o3yCyEKzg@mail.gmail.com>
References: <CAMKcwJuhf_MD87960tJohYomURb64F3w25Wk9pJw3o3yCyEKzg@mail.gmail.com>
Message-ID: <CAHC6v6goj5fcAg3C8iSZRf6uWUO0=_mczH=SMyFPQBUPARQWaQ@mail.gmail.com>

Hi,

did you run the setup.py with your custom python enterpreter ? can you
send the build output ?

Regards
Roman

2012/9/17 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi,
>
> I am building PySide from source on win7 32-bit using Python3.2.3,and I get
> the following error:
>
> -- Detecting CXX compiler ABI info - done
> CMake Error at
> c:/cmake28/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.
> cmake:97 (MESSAGE):
>   Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
> Call Stack (most recent call first):
>   c:/cmake28/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:288
> (_F
> PHSA_FAILURE_MESSAGE)
>   c:/cmake28/share/cmake-2.8/Modules/FindPythonInterp.cmake:139
> (FIND_PACKAGE_HA
> NDLE_STANDARD_ARGS)
>   CMakeLists.txt:5 (find_package)
>
>
> -- Configuring incomplete, errors occurred!
> setup.py:411: ResourceWarning: unclosed file <_io.TextIOWrapper name=4
> encoding=
> 'cp1252'>
>   if run_process(cmake_cmd, log) != 0:
> setup.py:411: ResourceWarning: unclosed file <_io.TextIOWrapper name=3
> encoding=
> 'cp1252'>
>   if run_process(cmake_cmd, log) != 0:
> error: Error configuring pyside-tools
>
>
> Why is CMake not able to find my python interpretor?
> I have set my custom path of python3.2 bin in PATH env variable correctly.
>
> (and the same builds fine on 64-bit machine)
> Am I missing something here?
>
> Regards,
> Tej.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From ameyadambir at gmail.com  Tue Sep 18 09:05:28 2012
From: ameyadambir at gmail.com (ameya dambir)
Date: Tue, 18 Sep 2012 12:35:28 +0530
Subject: [PySide] Failing Debug built
Message-ID: <CA+ec0Bq+TDFeiRsRX_O3koowBMNBHqwCmK72qXkNQCnB0cfddA@mail.gmail.com>

Hi,

I am trying to build debug version of PySide with Python3.2debug.

I am getting error at the end of installation:

SyntaxError: from __future__ imports must occur at the beginning of the file
CMake Error at CMakeLists.txt:27 (message):
  Could not detect Python module installation directory.

Where is this file? Do need to make change in it?

Ameya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120918/852699ca/attachment.html>

From gliblib247 at gmail.com  Fri Sep 21 20:36:49 2012
From: gliblib247 at gmail.com (Steve Payne)
Date: Fri, 21 Sep 2012 14:36:49 -0400
Subject: [PySide] QHostInfo.locateHost marked private in typesystem
Message-ID: <CAA0inxMZpPbxd_Cf949ndR39R_ULRvpecieTT4ctM5xm0q3r5g@mail.gmail.com>

I was looking for a convenient way to confirm the existence of a computer
on a local network and found documentation for QHostInfo.locateHost but in
the typesystem file for the network, locateHost is defined to be private?

Is there a particular reason locateHost is private?
Is there any way to use it without recompiling with it marked as public?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120921/efaa81a6/attachment.html>

From pyside at m.allo.ws  Sat Sep 22 19:13:26 2012
From: pyside at m.allo.ws (Zak)
Date: Sat, 22 Sep 2012 13:13:26 -0400
Subject: [PySide] What is required for a minimal installation of the runtime
	components?
Message-ID: <505DF1B6.500@m.allo.ws>

Hello PySide People,

I am building a Windows 7 PySide application for internal use only at my 
company, so complying with licenses, such as including source code, is 
not necessary, and installation does not have to be very convenient.

Currently, to install my PySide application, I need to download and 
install the entire Qt SDK version 1.2.1 for Windows, which is 1.7 GB. I 
download it from this page:

http://qt-project.org/downloads

Question 1. If I just want to install the runtime dependencies, and not 
the entire development kit, can I download one of the "Qt Library" 
packages from further down on that page?

Question 2. Do I want the MinGW, VS 2008, or VS 2010 version?

Question 3. I see that those downloads are .EXEs, so do I just run them 
to install the library?

Question 4. Because I am using PySide and not C++, do I actually need to 
install the whole 1.7 GB SDK for development? Could I have developed my 
PySide application just as easily with just the ~300 MB "Qt Library"? Or 
do I need the full SDK?

Currently, to install PySide, I need to download and install 
PySide-1.1.2.win32-py2.7.exe from this page:

http://qt-project.org/wiki/PySide_Binaries_Windows

I am guessing that in this case, the runtime dependencies are exactly 
the same as the development kit dependencies, so I still need to install 
this same thing even if I am just running the application, not 
developing it.

Question 5. Do I need to install PySide-1.1.2.win32-py2.7.exe for 
runtime, even if I am not developing? (I am guessing yes.)

Thank you,

Zak


From backup.rlacko at gmail.com  Sun Sep 23 00:46:12 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Sun, 23 Sep 2012 00:46:12 +0200
Subject: [PySide] What is required for a minimal installation of the
 runtime components?
In-Reply-To: <505DF1B6.500@m.allo.ws>
References: <505DF1B6.500@m.allo.ws>
Message-ID: <CAHC6v6gLnSNE7NNoxPde0TFD69mCh_wmFQoPOYaYVn=MFN8KHA@mail.gmail.com>

Hi,

To develop python application with PySide you need to downolad only
PySide binary distribution from here
http://qt-project.org/wiki/PySide_Binaries_Windows. This package
contains everyhing you need to develop and to run the application: the
Qt libs, Qt tools (designer, translator), and PySide libs and tools

You absolutely don't need the QT SDK, and You don't need the Qt library package.
You need only the Python and PySide package (for python 2.7 this one:
PySide-1.1.2.win32-py2.7.exe).

You would need the QT SDK (or Qt package) only if you create Qt C++
applications, or if you want to recompile pyside from source.

Regards
Roman

2012/9/22 Zak <pyside at m.allo.ws>:
> Hello PySide People,
>
> I am building a Windows 7 PySide application for internal use only at my
> company, so complying with licenses, such as including source code, is
> not necessary, and installation does not have to be very convenient.
>
> Currently, to install my PySide application, I need to download and
> install the entire Qt SDK version 1.2.1 for Windows, which is 1.7 GB. I
> download it from this page:
>
> http://qt-project.org/downloads
>
> Question 1. If I just want to install the runtime dependencies, and not
> the entire development kit, can I download one of the "Qt Library"
> packages from further down on that page?
>
> Question 2. Do I want the MinGW, VS 2008, or VS 2010 version?
>
> Question 3. I see that those downloads are .EXEs, so do I just run them
> to install the library?
>
> Question 4. Because I am using PySide and not C++, do I actually need to
> install the whole 1.7 GB SDK for development? Could I have developed my
> PySide application just as easily with just the ~300 MB "Qt Library"? Or
> do I need the full SDK?
>
> Currently, to install PySide, I need to download and install
> PySide-1.1.2.win32-py2.7.exe from this page:
>
> http://qt-project.org/wiki/PySide_Binaries_Windows
>
> I am guessing that in this case, the runtime dependencies are exactly
> the same as the development kit dependencies, so I still need to install
> this same thing even if I am just running the application, not
> developing it.
>
> Question 5. Do I need to install PySide-1.1.2.win32-py2.7.exe for
> runtime, even if I am not developing? (I am guessing yes.)
>
> Thank you,
>
> Zak
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From bb6xt at yahoo.com  Sun Sep 23 15:26:36 2012
From: bb6xt at yahoo.com (bb6xt at yahoo.com)
Date: Sat, 23 Sep 2012 14:26:36 +0100
Subject: [PySide] What is required for a minimal installation of the
	runtime components?
Message-ID: <715457.28704.bm@smtp217.mail.ne1.yahoo.com>

I am assuming you can run the application on your dev machine (ie python main.py). If that is the case it means you have all the dependencies on that machine. Download pyinstaller (pls just google it as I don't remember the link now). Extract to any directory of your choice. Cd into the directory containing your source code and run $python path\to\pyinstaller\Configure.py
$python path\to\pyinstaller\Makespec.py main_script_for_your_app.py -n appname
$python path\to\pyinstaller\Build.py appname.spec
this will create appname.exe which is a standalone exe that can run on any pc without python or pyside or qt. Pyinstaller will bundle **ALL** dependencies and hence nothing else is required. You may use NSis or some other tool to create a simple installer If you like.

--------------------------
Sent from my mobile device

From pyside at m.allo.ws  Sun Sep 23 16:03:36 2012
From: pyside at m.allo.ws (Zak)
Date: Sun, 23 Sep 2012 10:03:36 -0400
Subject: [PySide] What is required for a minimal installation of the
 runtime components?
In-Reply-To: <505F161C.6040001@m.allo.ws>
References: <505DF1B6.500@m.allo.ws>
	<CAHC6v6gLnSNE7NNoxPde0TFD69mCh_wmFQoPOYaYVn=MFN8KHA@mail.gmail.com>
	<505F161C.6040001@m.allo.ws>
Message-ID: <505F16B8.5000202@m.allo.ws>

Thank you for that information. I feel a bit silly for downloading the 
1.7 GB Qt SDK, now. The reason I thought I needed it was this page:

http://qt-project.org/wiki/Setting_up_PySide

Which says """To set up PySide, you need:

1. Qt
2. Python
3. PySide"""

I interpreted that as meaning that I needed to install those things each 
separately, I didn't know (1) was built into (3).

Zak


From backup.rlacko at gmail.com  Sun Sep 23 18:51:49 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Sun, 23 Sep 2012 18:51:49 +0200
Subject: [PySide] What is required for a minimal installation of the
 runtime components?
In-Reply-To: <505F16B8.5000202@m.allo.ws>
References: <505DF1B6.500@m.allo.ws>
	<CAHC6v6gLnSNE7NNoxPde0TFD69mCh_wmFQoPOYaYVn=MFN8KHA@mail.gmail.com>
	<505F161C.6040001@m.allo.ws> <505F16B8.5000202@m.allo.ws>
Message-ID: <CAHC6v6io6X9R0ZmQ8Nph84nZeaORBUSkqC9B_r4K0k8Fdg-+Rw@mail.gmail.com>

Hi,

2012/9/23 Zak <pyside at m.allo.ws>:
> Thank you for that information. I feel a bit silly for downloading the
> 1.7 GB Qt SDK, now. The reason I thought I needed it was this page:
>
> http://qt-project.org/wiki/Setting_up_PySide

to install PySide under windows You should read this site:
  http://qt-project.org/wiki/PySide_Binaries_Windows

to build PySide from source read this:
  http://qt-project.org/wiki/Building_PySide_on_Windows

>
> Which says """To set up PySide, you need:
>
> 1. Qt
> 2. Python
> 3. PySide"""
>
> I interpreted that as meaning that I needed to install those things each
> separately, I didn't know (1) was built into (3).

R.

>
> Zak
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From niki.spahiev at gmail.com  Tue Sep 25 14:45:18 2012
From: niki.spahiev at gmail.com (=?UTF-8?B?0J3QuNC60L7Qu9Cw0Lk=?=)
Date: Tue, 25 Sep 2012 15:45:18 +0300
Subject: [PySide] Using GLC_lib & PySide
Message-ID: <CAFoopHSMJrp=3zjAdLDMdGnMV-AECVXYsak9ebF7sKcVuUw78A@mail.gmail.com>

Hello,

Small demo of using GLC_lib http://www.glc-lib.net can be found at
http://http://sourceforge.net/projects/pyglc/

Niki
http://www.vintech.bg
-- 
|  (\_/)  This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Снимка от 2012-09-25 15:43:15.png
Type: image/png
Size: 129747 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120925/0fbcd146/attachment.png>

From hugo.lima at openbossa.org  Tue Sep 25 16:22:42 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Tue, 25 Sep 2012 11:22:42 -0300
Subject: [PySide] PySide website down
Message-ID: <2741920.NSFmnYkgdy@hugodesktop>

Hi,

PySide website is down since yesterday, the current site was running on a 
virtual machine hosted by Nokia.

Luciano is trying to contact someone on Nokia to know if the website can stay 
there, hosted on Nokia, or if we need to find a new home.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120925/f56c553c/attachment.sig>

From vasure at gmail.com  Tue Sep 25 21:31:50 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Tue, 25 Sep 2012 12:31:50 -0700
Subject: [PySide] PySide website down
In-Reply-To: <2741920.NSFmnYkgdy@hugodesktop>
References: <2741920.NSFmnYkgdy@hugodesktop>
Message-ID: <CAG_nbnuEdzm9GEpfY-csj5_odFHBMVs6_9rxX1U4n3_A0X0u+A@mail.gmail.com>

There is a local Qt meet up schedule tomorrow with Juhapekka Niemi
http://www.meetup.com/QtChapterSiliconValley/events/78487092/ Do you
think I should bring this up so that we can get some resources?

Also, are the docs part of the gitorious code checkin?

On Tue, Sep 25, 2012 at 7:22 AM, Hugo Parente Lima
<hugo.lima at openbossa.org> wrote:
>
> Hi,
>
> PySide website is down since yesterday, the current site was running on a
> virtual machine hosted by Nokia.
>
> Luciano is trying to contact someone on Nokia to know if the website can stay
> there, hosted on Nokia, or if we need to find a new home.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From anderson.lizardo at openbossa.org  Tue Sep 25 22:40:14 2012
From: anderson.lizardo at openbossa.org (Anderson Lizardo)
Date: Tue, 25 Sep 2012 16:40:14 -0400
Subject: [PySide] PySide website down
In-Reply-To: <2741920.NSFmnYkgdy@hugodesktop>
References: <2741920.NSFmnYkgdy@hugodesktop>
Message-ID: <CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>

Hi,

On Tue, Sep 25, 2012 at 10:22 AM, Hugo Parente Lima
<hugo.lima at openbossa.org> wrote:
> Hi,
>
> PySide website is down since yesterday, the current site was running on a
> virtual machine hosted by Nokia.
>
> Luciano is trying to contact someone on Nokia to know if the website can stay
> there, hosted on Nokia, or if we need to find a new home.

For those looking for the latest release (1.1.2) and pyside-tools,
fortunately PySide can be found in many distros/OSes, so the source is
"mirrored" in many places. E.g:

https://distfiles.macports.org/py-shiboken/shiboken-1.1.2.tar.bz2
(SHA1: 2ffe9d47a3f536840ed9d7eff766a53040bb2a2e)

https://distfiles.macports.org/py-pyside/pyside-qt4.8+1.1.2.tar.bz2
(SHA1: c0119775f2500e48efebdd50b7be7543e71b2c24)

https://distfiles.macports.org/py-pyside-tools/pyside-tools-0.2.14.tar.bz2
(SHA1: f654553bc9bfb35dbc5673da26830969393f9fe8)

(I could not find reliable sources for pyside-mobility, but I suspect
it is not maintained anymore because last release was on 2011).

Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil


From hugo.lima at openbossa.org  Tue Sep 25 22:45:28 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Tue, 25 Sep 2012 17:45:28 -0300
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnuEdzm9GEpfY-csj5_odFHBMVs6_9rxX1U4n3_A0X0u+A@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAG_nbnuEdzm9GEpfY-csj5_odFHBMVs6_9rxX1U4n3_A0X0u+A@mail.gmail.com>
Message-ID: <1378432.ETvRfImRsB@hugodesktop>

On Tuesday, September 25, 2012 12:31:50 PM Srini Kommoori wrote:
> There is a local Qt meet up schedule tomorrow with Juhapekka Niemi
> http://www.meetup.com/QtChapterSiliconValley/events/78487092/ Do you
> think I should bring this up so that we can get some resources?

Yep, for sure, we need a place to stay.
 
> Also, are the docs part of the gitorious code checkin?

The docs were in the website too, but they can be auto-generated from the code 
on our git repository.
 
> On Tue, Sep 25, 2012 at 7:22 AM, Hugo Parente Lima
> 
> <hugo.lima at openbossa.org> wrote:
> > Hi,
> > 
> > PySide website is down since yesterday, the current site was running on a
> > virtual machine hosted by Nokia.
> > 
> > Luciano is trying to contact someone on Nokia to know if the website can
> > stay there, hosted on Nokia, or if we need to find a new home.
> > 
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120925/0b072d7a/attachment.sig>

From vasure at gmail.com  Tue Sep 25 23:40:10 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Tue, 25 Sep 2012 14:40:10 -0700
Subject: [PySide] PySide website down
In-Reply-To: <1378432.ETvRfImRsB@hugodesktop>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAG_nbnuEdzm9GEpfY-csj5_odFHBMVs6_9rxX1U4n3_A0X0u+A@mail.gmail.com>
	<1378432.ETvRfImRsB@hugodesktop>
Message-ID: <CAG_nbnuY3XY-PJb9Ns3AgyvbafrfVJ0twfF2H_xv5PT5j_hW7A@mail.gmail.com>

If you can generate docs(or send instructions), I could post them to
github for free hosting.

Looking at the google cache,
http://webcache.googleusercontent.com/search?q=cache:http://www.pyside.org/
Apart from Documentation and Downloads, everything can be recreated
easily.

On Tue, Sep 25, 2012 at 1:45 PM, Hugo Parente Lima
<hugo.lima at openbossa.org> wrote:
> On Tuesday, September 25, 2012 12:31:50 PM Srini Kommoori wrote:
>> There is a local Qt meet up schedule tomorrow with Juhapekka Niemi
>> http://www.meetup.com/QtChapterSiliconValley/events/78487092/ Do you
>> think I should bring this up so that we can get some resources?
>
> Yep, for sure, we need a place to stay.
>
>> Also, are the docs part of the gitorious code checkin?
>
> The docs were in the website too, but they can be auto-generated from the code
> on our git repository.
>
>> On Tue, Sep 25, 2012 at 7:22 AM, Hugo Parente Lima
>>
>> <hugo.lima at openbossa.org> wrote:
>> > Hi,
>> >
>> > PySide website is down since yesterday, the current site was running on a
>> > virtual machine hosted by Nokia.
>> >
>> > Luciano is trying to contact someone on Nokia to know if the website can
>> > stay there, hosted on Nokia, or if we need to find a new home.
>> >
>> > _______________________________________________
>> > PySide mailing list
>> > PySide at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/pyside


From ltanure at gmail.com  Tue Sep 25 23:49:34 2012
From: ltanure at gmail.com (Lucas Tanure)
Date: Tue, 25 Sep 2012 18:49:34 -0300
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnuY3XY-PJb9Ns3AgyvbafrfVJ0twfF2H_xv5PT5j_hW7A@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAG_nbnuEdzm9GEpfY-csj5_odFHBMVs6_9rxX1U4n3_A0X0u+A@mail.gmail.com>
	<1378432.ETvRfImRsB@hugodesktop>
	<CAG_nbnuY3XY-PJb9Ns3AgyvbafrfVJ0twfF2H_xv5PT5j_hW7A@mail.gmail.com>
Message-ID: <CAJyon0vwzwTzqt27Y-QysdD1O55QWP4w1+eq0QEUnoU+C_gCNg@mail.gmail.com>

Digia said something about pyside?

Lucas A. Tanure Alves
Skype : lucas.tanure
+55 (19) 88176559
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120925/58201e52/attachment.html>

From vasure at gmail.com  Wed Sep 26 00:50:46 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Tue, 25 Sep 2012 15:50:46 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAJyon0vwzwTzqt27Y-QysdD1O55QWP4w1+eq0QEUnoU+C_gCNg@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAG_nbnuEdzm9GEpfY-csj5_odFHBMVs6_9rxX1U4n3_A0X0u+A@mail.gmail.com>
	<1378432.ETvRfImRsB@hugodesktop>
	<CAG_nbnuY3XY-PJb9Ns3AgyvbafrfVJ0twfF2H_xv5PT5j_hW7A@mail.gmail.com>
	<CAJyon0vwzwTzqt27Y-QysdD1O55QWP4w1+eq0QEUnoU+C_gCNg@mail.gmail.com>
Message-ID: <CAG_nbns_Puw=ehXEovCXmAHXBdY2Ff3+5icsZ7qB95xbfhjSxA@mail.gmail.com>

No Digia didn't say anything about PySide. I will bring this up
tomorrow when we meet.

On Tue, Sep 25, 2012 at 2:49 PM, Lucas Tanure <ltanure at gmail.com> wrote:
> Digia said something about pyside?
>
> Lucas A. Tanure Alves
> Skype : lucas.tanure
> +55 (19) 88176559
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From jmccampbell at enthought.com  Wed Sep 26 22:07:32 2012
From: jmccampbell at enthought.com (Jason McCampbell)
Date: Wed, 26 Sep 2012 15:07:32 -0500
Subject: [PySide] PySide website down
In-Reply-To: <CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
Message-ID: <CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>

On Tue, Sep 25, 2012 at 3:40 PM, Anderson Lizardo <
anderson.lizardo at openbossa.org> wrote:

> For those looking for the latest release (1.1.2) and pyside-tools,
> fortunately PySide can be found in many distros/OSes, so the source is
> "mirrored" in many places. E.g:
>
> https://distfiles.macports.org/py-shiboken/shiboken-1.1.2.tar.bz2
> (SHA1: 2ffe9d47a3f536840ed9d7eff766a53040bb2a2e)
>
> https://distfiles.macports.org/py-pyside/pyside-qt4.8+1.1.2.tar.bz2
> (SHA1: c0119775f2500e48efebdd50b7be7543e71b2c24)
>
> https://distfiles.macports.org/py-pyside-tools/pyside-tools-0.2.14.tar.bz2
> (SHA1: f654553bc9bfb35dbc5673da26830969393f9fe8)
>

This is very helpful, thanks.  I am also trying to update my local source
tree from the current development trunk.  Is it correct to pull from
https://codereview.qt-project.org/p/pyside/*?  If so, is there a current
version of the build scripts repo or has that been replaced by the
pyside-setup code?  I was able to pull from pyside and shiboken but not the
builds scripts.

Thanks,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120926/98cf63ac/attachment.html>

From backup.rlacko at gmail.com  Thu Sep 27 10:28:11 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Thu, 27 Sep 2012 10:28:11 +0200
Subject: [PySide] PySide website down
In-Reply-To: <CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
Message-ID: <CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>

Hi,

2012/9/26 Jason McCampbell <jmccampbell at enthought.com>:
> On Tue, Sep 25, 2012 at 3:40 PM, Anderson Lizardo
> <anderson.lizardo at openbossa.org> wrote:
>>
>> For those looking for the latest release (1.1.2) and pyside-tools,
>> fortunately PySide can be found in many distros/OSes, so the source is
>> "mirrored" in many places. E.g:
>>
>> https://distfiles.macports.org/py-shiboken/shiboken-1.1.2.tar.bz2
>> (SHA1: 2ffe9d47a3f536840ed9d7eff766a53040bb2a2e)
>>
>> https://distfiles.macports.org/py-pyside/pyside-qt4.8+1.1.2.tar.bz2
>> (SHA1: c0119775f2500e48efebdd50b7be7543e71b2c24)
>>
>> https://distfiles.macports.org/py-pyside-tools/pyside-tools-0.2.14.tar.bz2
>> (SHA1: f654553bc9bfb35dbc5673da26830969393f9fe8)
>
>
> This is very helpful, thanks.  I am also trying to update my local source
> tree from the current development trunk.  Is it correct to pull from
> https://codereview.qt-project.org/p/pyside/*?  If so, is there a current
> version of the build scripts repo or has that been replaced by the
> pyside-setup code?  I was able to pull from pyside and shiboken but not the
> builds scripts.

Yes you should allways pull PySide sources from
https://codereview.qt-project.org/p/pyside/*

The pyside-setup build scripts is available only on github here
https://github.com/PySide/pyside-setup

R.

>
> Thanks,
> Jason
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From vasure at gmail.com  Thu Sep 27 21:43:18 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Thu, 27 Sep 2012 12:43:18 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
Message-ID: <CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>

Hi Guys,

Can we get hold of Matti Airas for domain transfer?
http://www.networksolutions.com/whois-search/pyside.org

I have talked to few folks at Digia to get the site transferred. I
will send them the information so that they can track down the
machine/vpc.

Matti, If you are still on the mailing list, please guide us through.

thanks,
-Srini

On Thu, Sep 27, 2012 at 1:28 AM, Roman Lacko <backup.rlacko at gmail.com> wrote:
> Hi,
>
> 2012/9/26 Jason McCampbell <jmccampbell at enthought.com>:
>> On Tue, Sep 25, 2012 at 3:40 PM, Anderson Lizardo
>> <anderson.lizardo at openbossa.org> wrote:
>>>
>>> For those looking for the latest release (1.1.2) and pyside-tools,
>>> fortunately PySide can be found in many distros/OSes, so the source is
>>> "mirrored" in many places. E.g:
>>>
>>> https://distfiles.macports.org/py-shiboken/shiboken-1.1.2.tar.bz2
>>> (SHA1: 2ffe9d47a3f536840ed9d7eff766a53040bb2a2e)
>>>
>>> https://distfiles.macports.org/py-pyside/pyside-qt4.8+1.1.2.tar.bz2
>>> (SHA1: c0119775f2500e48efebdd50b7be7543e71b2c24)
>>>
>>> https://distfiles.macports.org/py-pyside-tools/pyside-tools-0.2.14.tar.bz2
>>> (SHA1: f654553bc9bfb35dbc5673da26830969393f9fe8)
>>
>>
>> This is very helpful, thanks.  I am also trying to update my local source
>> tree from the current development trunk.  Is it correct to pull from
>> https://codereview.qt-project.org/p/pyside/*?  If so, is there a current
>> version of the build scripts repo or has that been replaced by the
>> pyside-setup code?  I was able to pull from pyside and shiboken but not the
>> builds scripts.
>
> Yes you should allways pull PySide sources from
> https://codereview.qt-project.org/p/pyside/*
>
> The pyside-setup build scripts is available only on github here
> https://github.com/PySide/pyside-setup
>
> R.
>
>>
>> Thanks,
>> Jason
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From andyfaff at gmail.com  Fri Sep 28 00:32:41 2012
From: andyfaff at gmail.com (Andrew Nelson)
Date: Fri, 28 Sep 2012 08:32:41 +1000
Subject: [PySide]  PySide website down
Message-ID: <CAAbtOZdy2TLgOzhfRWF0PAYwZf2oTEu05pS1j+kjUcndFC+xSQ@mail.gmail.com>

Dear pysiders,
 I'm just getting started with PySide and Python. I really like this
binding for Qt. I appreciate the effort that is going into creating
this code.

However, for a starter like me it's a real hurdle not having the
website available for all the documentation, especially the class
references. From the archive I know that work is going into getting
the website transferred, I just wanted to say that I've got my fingers
and toes crossed that it'll happen soon.

cheers,
Andrew.

-- 
_____________________________________
Dr. Andrew Nelson


_____________________________________


From vasure at gmail.com  Fri Sep 28 01:34:53 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Thu, 27 Sep 2012 16:34:53 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAAbtOZdy2TLgOzhfRWF0PAYwZf2oTEu05pS1j+kjUcndFC+xSQ@mail.gmail.com>
References: <CAAbtOZdy2TLgOzhfRWF0PAYwZf2oTEu05pS1j+kjUcndFC+xSQ@mail.gmail.com>
Message-ID: <CAG_nbnu6KMPX-uj4_vs49N4Pj5p8Lfgcjp+uS_4zj9OL29xiyg@mail.gmail.com>

Andrew, We hear you. We are doing everything we can. Worst case,
expect a temporary docs location by tomorrow.

-Srini

On Thu, Sep 27, 2012 at 3:32 PM, Andrew Nelson <andyfaff at gmail.com> wrote:
> Dear pysiders,
>  I'm just getting started with PySide and Python. I really like this
> binding for Qt. I appreciate the effort that is going into creating
> this code.
>
> However, for a starter like me it's a real hurdle not having the
> website available for all the documentation, especially the class
> references. From the archive I know that work is going into getting
> the website transferred, I just wanted to say that I've got my fingers
> and toes crossed that it'll happen soon.
>
> cheers,
> Andrew.
>
> --
> _____________________________________
> Dr. Andrew Nelson
>
>
> _____________________________________
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


From vasure at gmail.com  Fri Sep 28 03:01:08 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Thu, 27 Sep 2012 18:01:08 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnu6KMPX-uj4_vs49N4Pj5p8Lfgcjp+uS_4zj9OL29xiyg@mail.gmail.com>
References: <CAAbtOZdy2TLgOzhfRWF0PAYwZf2oTEu05pS1j+kjUcndFC+xSQ@mail.gmail.com>
	<CAG_nbnu6KMPX-uj4_vs49N4Pj5p8Lfgcjp+uS_4zj9OL29xiyg@mail.gmail.com>
Message-ID: <CAG_nbnsx4+6u70MOHHmdvjM4Rbe07tphiUJNj8hMMMS5RVcO1w@mail.gmail.com>

Here are temporary docs.

http://srinikom.github.com/pyside-docs/

. Search won't work as we are hosting them as static files.
. Hope that is useful. I couldn't generate 1.1.2 docs so I just posted
1.0.7 from a local copy.

-Srini

On Thu, Sep 27, 2012 at 4:34 PM, Srini Kommoori <vasure at gmail.com> wrote:
> Andrew, We hear you. We are doing everything we can. Worst case,
> expect a temporary docs location by tomorrow.
>
> -Srini
>
> On Thu, Sep 27, 2012 at 3:32 PM, Andrew Nelson <andyfaff at gmail.com> wrote:
>> Dear pysiders,
>>  I'm just getting started with PySide and Python. I really like this
>> binding for Qt. I appreciate the effort that is going into creating
>> this code.
>>
>> However, for a starter like me it's a real hurdle not having the
>> website available for all the documentation, especially the class
>> references. From the archive I know that work is going into getting
>> the website transferred, I just wanted to say that I've got my fingers
>> and toes crossed that it'll happen soon.
>>
>> cheers,
>> Andrew.
>>
>> --
>> _____________________________________
>> Dr. Andrew Nelson
>>
>>
>> _____________________________________
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside


From mairas at iki.fi  Fri Sep 28 10:01:02 2012
From: mairas at iki.fi (Matti Airas)
Date: Fri, 28 Sep 2012 11:01:02 +0300
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
Message-ID: <CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>

Hi,

Unfortunately the WHOIS information is not correct. The domain was moved
from Nokia Meego (where I worked) to Qt Project around March or April, but
for some reason the Qt admins decided to put my information as the owner. I
no longer work at Nokia and have no access there.

Hugo and Luciano gave me a heads-up about the virtual server being down.
There's probably nothing that can be done about that, but the plan was
anyway that Qt Project admins would create a redirect from pyside.org to
the PySide wiki front page, and provide hosting for the static pages. I've
tried emailing Qt about the issue as well, but got no reply so far. Next,
some good ole' phone calls...

If the consensus is that being part of Qt Project is actually harmful for
PySide (due to issues like the current one), we could of course try to
discuss with Qt Project about getting the ownership of the domain ourselves
(dunno who should be the right owner?). Or, a bit more than year ago, when
trying to figure out the eventual home for PySide, I was also discussing
with PSF, and they would've been willing, but Qt proposed the current
setup, and at the time I thought it would be a great idea. PSF probably
would be still willing, but if I recall correctly, that'd require a
copyright assignment to PSF from all contributors, and I still have painful
memories about the Qt contributor license agreement hassle... :-/

Cheers,

ma.

On 27 September 2012 22:43, Srini Kommoori <vasure at gmail.com> wrote:

> Hi Guys,
>
> Can we get hold of Matti Airas for domain transfer?
> http://www.networksolutions.com/whois-search/pyside.org
>
> I have talked to few folks at Digia to get the site transferred. I
> will send them the information so that they can track down the
> machine/vpc.
>
> Matti, If you are still on the mailing list, please guide us through.
>
> thanks,
> -Srini
>
> On Thu, Sep 27, 2012 at 1:28 AM, Roman Lacko <backup.rlacko at gmail.com>
> wrote:
> > Hi,
> >
> > 2012/9/26 Jason McCampbell <jmccampbell at enthought.com>:
> >> On Tue, Sep 25, 2012 at 3:40 PM, Anderson Lizardo
> >> <anderson.lizardo at openbossa.org> wrote:
> >>>
> >>> For those looking for the latest release (1.1.2) and pyside-tools,
> >>> fortunately PySide can be found in many distros/OSes, so the source is
> >>> "mirrored" in many places. E.g:
> >>>
> >>> https://distfiles.macports.org/py-shiboken/shiboken-1.1.2.tar.bz2
> >>> (SHA1: 2ffe9d47a3f536840ed9d7eff766a53040bb2a2e)
> >>>
> >>> https://distfiles.macports.org/py-pyside/pyside-qt4.8+1.1.2.tar.bz2
> >>> (SHA1: c0119775f2500e48efebdd50b7be7543e71b2c24)
> >>>
> >>>
> https://distfiles.macports.org/py-pyside-tools/pyside-tools-0.2.14.tar.bz2
> >>> (SHA1: f654553bc9bfb35dbc5673da26830969393f9fe8)
> >>
> >>
> >> This is very helpful, thanks.  I am also trying to update my local
> source
> >> tree from the current development trunk.  Is it correct to pull from
> >> https://codereview.qt-project.org/p/pyside/*?  If so, is there a
> current
> >> version of the build scripts repo or has that been replaced by the
> >> pyside-setup code?  I was able to pull from pyside and shiboken but not
> the
> >> builds scripts.
> >
> > Yes you should allways pull PySide sources from
> > https://codereview.qt-project.org/p/pyside/*
> >
> > The pyside-setup build scripts is available only on github here
> > https://github.com/PySide/pyside-setup
> >
> > R.
> >
> >>
> >> Thanks,
> >> Jason
> >>
> >> _______________________________________________
> >> PySide mailing list
> >> PySide at qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/pyside
> >>
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/56b5c569/attachment.html>

From tejashri.kandolkar at gmail.com  Fri Sep 28 10:27:58 2012
From: tejashri.kandolkar at gmail.com (Tejashri Kandolkar)
Date: Fri, 28 Sep 2012 13:57:58 +0530
Subject: [PySide] Can PySide run with Qt DLLs in another location other than
	Lib\site-packages\PySide\
Message-ID: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>

Hi,

After installing PySide1.1.2, I see that all the qt DLL's are getting
copied in the ...\python_3_2\release\Lib\site-packages\PySide\  directory
Can I have PySide run without the Qt DLL's in the
...\Lib\site-packages\PySide\ directory, but some\other\directory\...

If yes, then whats the change that needs to be taken care of while building
PySide? (There should be some change in cmake scripts I suppose but not
sure where.)

I am interested in this because I already have the Qt DLLs present in a top
level directory, and copying the same DLLs again in the PySide dir is a
duplication.

Regards,
Tej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/6a4e2cd9/attachment.html>

From bjelge at nefines.com  Fri Sep 28 10:49:12 2012
From: bjelge at nefines.com (=?ISO-8859-1?Q?Bj=F8rn_Helge_Kj=F8snes?=)
Date: Fri, 28 Sep 2012 10:49:12 +0200
Subject: [PySide] Can PySide run with Qt DLLs in another location other
 than Lib\site-packages\PySide\
In-Reply-To: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
References: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
Message-ID: <50656488.5060707@nefines.com>

Hi,

try tor create a qt.conf file in the same directory as you have the 
pyside pyd files.

The content should be:
[Paths]
Prefix = YourPythonDir/Lib/site-packages/PySide
Binaries = Your QT Dir/bin
Plugins = Your QT Dir/plugins
Translation = translation

Kind regards,
Bjørn Helge Kjøsnes

On 28.09.2012 10:27, Tejashri Kandolkar wrote:
> Hi,
>
> After installing PySide1.1.2, I see that all the qt DLL's are getting 
> copied in the ...\python_3_2\release\Lib\site-packages\PySide\  directory
> Can I have PySide run without the Qt DLL's in the 
> ...\Lib\site-packages\PySide\ directory, but some\other\directory\...
>
> If yes, then whats the change that needs to be taken care of while 
> building PySide? (There should be some change in cmake scripts I 
> suppose but not sure where.)
>
> I am interested in this because I already have the Qt DLLs present in 
> a top level directory, and copying the same DLLs again in the PySide 
> dir is a duplication.
>
> Regards,
> Tej
>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/d9424f89/attachment.html>

From backup.rlacko at gmail.com  Fri Sep 28 10:56:35 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Fri, 28 Sep 2012 10:56:35 +0200
Subject: [PySide] Can PySide run with Qt DLLs in another location other
 than Lib\site-packages\PySide\
In-Reply-To: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
References: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
Message-ID: <CAHC6v6jrhmL2Fh+V4ca2Z0NS8GEJA+Dp5JjEr_D2y1OfAMzUTw@mail.gmail.com>

Hi,
yes you can have qt on different location.
Here is simple howto:

1. install PySide

2. move following Qt files and directories from PySide to new
location, for example to C:\QtDist:

Qt dirs:
plugins
scripts
translations
typesystems
examples
imports
include

Qt files:
designer.exe
lconvert.exe
libeay32.dll
linguist.exe
lrelease.exe
lupdate.exe
phonon4.dll
Qt3Support4.dll
QtCLucene4.dll
QtCore4.dll
QtDeclarative4.dll
QtDesigner4.dll
QtDesignerComponents4.dll
QtGui4.dll
QtHelp4.dll
QtMultimedia4.dll
QtNetwork4.dll
QtOpenGL4.dll
QtScript4.dll
QtScriptTools4.dll
QtSql4.dll
QtSvg4.dll
QtTest4.dll
QtWebKit4.dll
QtXml4.dll
QtXmlPatterns4.dll
ssleay32.dll

3. edit qt.conf file, change this:
  C:/Python27/Lib/site-packages/
to this:
  C:/
so it looks like:
  [Paths]
  Prefix = C:/QtDist
  Binaries = C:/QtDist
  Plugins = C:/QtDist/plugins
  Translations = C:/QtDist/translations

4. add C:\QtDist to PATH environment variable

5. start coding :)

Regards
R.

2012/9/28 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi,
>
> After installing PySide1.1.2, I see that all the qt DLL's are getting copied
> in the ...\python_3_2\release\Lib\site-packages\PySide\  directory
> Can I have PySide run without the Qt DLL's in the
> ...\Lib\site-packages\PySide\ directory, but some\other\directory\...
>
> If yes, then whats the change that needs to be taken care of while building
> PySide? (There should be some change in cmake scripts I suppose but not sure
> where.)
>
> I am interested in this because I already have the Qt DLLs present in a top
> level directory, and copying the same DLLs again in the PySide dir is a
> duplication.
>
> Regards,
> Tej
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From backup.rlacko at gmail.com  Fri Sep 28 10:58:58 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Fri, 28 Sep 2012 10:58:58 +0200
Subject: [PySide] Can PySide run with Qt DLLs in another location other
 than Lib\site-packages\PySide\
In-Reply-To: <CAHC6v6jrhmL2Fh+V4ca2Z0NS8GEJA+Dp5JjEr_D2y1OfAMzUTw@mail.gmail.com>
References: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
	<CAHC6v6jrhmL2Fh+V4ca2Z0NS8GEJA+Dp5JjEr_D2y1OfAMzUTw@mail.gmail.com>
Message-ID: <CAHC6v6j1HtMDrKdt-4bZ0BLZoEdg05Ffm9AoUrEqsTWV+FjXPQ@mail.gmail.com>

fixed path in qt.conf,  see bellow, step 3.

2012/9/28 Roman Lacko <backup.rlacko at gmail.com>:
> Hi,
> yes you can have qt on different location.
> Here is simple howto:
>
> 1. install PySide
>
> 2. move following Qt files and directories from PySide to new
> location, for example to C:\QtDist:
>
> Qt dirs:
> plugins
> scripts
> translations
> typesystems
> examples
> imports
> include
>
> Qt files:
> designer.exe
> lconvert.exe
> libeay32.dll
> linguist.exe
> lrelease.exe
> lupdate.exe
> phonon4.dll
> Qt3Support4.dll
> QtCLucene4.dll
> QtCore4.dll
> QtDeclarative4.dll
> QtDesigner4.dll
> QtDesignerComponents4.dll
> QtGui4.dll
> QtHelp4.dll
> QtMultimedia4.dll
> QtNetwork4.dll
> QtOpenGL4.dll
> QtScript4.dll
> QtScriptTools4.dll
> QtSql4.dll
> QtSvg4.dll
> QtTest4.dll
> QtWebKit4.dll
> QtXml4.dll
> QtXmlPatterns4.dll
> ssleay32.dll
>
> 3. edit qt.conf file, change this:
>   C:/Python27/Lib/site-packages/
> to this:
>   C:/
   C:/QtDist

> so it looks like:
>   [Paths]
>   Prefix = C:/QtDist
>   Binaries = C:/QtDist
>   Plugins = C:/QtDist/plugins
>   Translations = C:/QtDist/translations
>
> 4. add C:\QtDist to PATH environment variable
>
> 5. start coding :)
>
> Regards
> R.
>
> 2012/9/28 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
>> Hi,
>>
>> After installing PySide1.1.2, I see that all the qt DLL's are getting copied
>> in the ...\python_3_2\release\Lib\site-packages\PySide\  directory
>> Can I have PySide run without the Qt DLL's in the
>> ...\Lib\site-packages\PySide\ directory, but some\other\directory\...
>>
>> If yes, then whats the change that needs to be taken care of while building
>> PySide? (There should be some change in cmake scripts I suppose but not sure
>> where.)
>>
>> I am interested in this because I already have the Qt DLLs present in a top
>> level directory, and copying the same DLLs again in the PySide dir is a
>> duplication.
>>
>> Regards,
>> Tej
>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>


From backup.rlacko at gmail.com  Fri Sep 28 11:10:37 2012
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Fri, 28 Sep 2012 11:10:37 +0200
Subject: [PySide] Can PySide run with Qt DLLs in another location other
 than Lib\site-packages\PySide\
In-Reply-To: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
References: <CAMKcwJurFhr+B4_41bC1qDNTte_CqYcOKBazCr0St=pvKBj-Hg@mail.gmail.com>
Message-ID: <CAHC6v6jQGQif_ze9oDQu3TaWazMnUpsna4f7TRteqgcfmzjUAA@mail.gmail.com>

Hi,

just one note on sharing Qt DLLs, I don't recommend to share Qt DLLs
in one directory because you need to add that dir to PATH environment
variable so PySide can find the DLLs.

If Qt DLLs are in PySide dir you can install more PySide versions
built against different Qt versions. And You can install PySide in
virtualenv.

Regards
R.

2012/9/28 Tejashri Kandolkar <tejashri.kandolkar at gmail.com>:
> Hi,
>
> After installing PySide1.1.2, I see that all the qt DLL's are getting copied
> in the ...\python_3_2\release\Lib\site-packages\PySide\  directory
> Can I have PySide run without the Qt DLL's in the
> ...\Lib\site-packages\PySide\ directory, but some\other\directory\...
>
> If yes, then whats the change that needs to be taken care of while building
> PySide? (There should be some change in cmake scripts I suppose but not sure
> where.)
>
> I am interested in this because I already have the Qt DLLs present in a top
> level directory, and copying the same DLLs again in the PySide dir is a
> duplication.
>
> Regards,
> Tej
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>


From ltanure at gmail.com  Fri Sep 28 13:51:00 2012
From: ltanure at gmail.com (Lucas Tanure)
Date: Fri, 28 Sep 2012 08:51:00 -0300
Subject: [PySide] PySide website down
In-Reply-To: <CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
Message-ID: <CAJyon0v8Aru0+hLNDRnH9k+mQUXaWjRs5XwYbff3yiyoGZVv5A@mail.gmail.com>

Can we go to Amazon servers ? How much you think will cost?


Lucas A. Tanure Alves
Skype : lucas.tanure
+55 (19) 88176559
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/b2df248c/attachment.html>

From sdeibel at wingware.com  Fri Sep 28 14:07:08 2012
From: sdeibel at wingware.com (Stephan Deibel)
Date: Fri, 28 Sep 2012 08:07:08 -0400
Subject: [PySide] PySide website down
In-Reply-To: <CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
Message-ID: <506592EC.5070306@wingware.com>

Matti Airas wrote:
> Unfortunately the WHOIS information is not correct. The domain was 
> moved from Nokia Meego (where I worked) to Qt Project around March or 
> April, but for some reason the Qt admins decided to put my information 
> as the owner. I no longer work at Nokia and have no access there.
>
> Hugo and Luciano gave me a heads-up about the virtual server being 
> down. There's probably nothing that can be done about that, but the 
> plan was anyway that Qt Project admins would create a redirect from 
> pyside.org <http://pyside.org> to the PySide wiki front page, and 
> provide hosting for the static pages. I've tried emailing Qt about the 
> issue as well, but got no reply so far. Next, some good ole' phone 
> calls...
>
> If the consensus is that being part of Qt Project is actually harmful 
> for PySide (due to issues like the current one), we could of course 
> try to discuss with Qt Project about getting the ownership of the 
> domain ourselves (dunno who should be the right owner?). Or, a bit 
> more than year ago, when trying to figure out the eventual home for 
> PySide, I was also discussing with PSF, and they would've been 
> willing, but Qt proposed the current setup, and at the time I thought 
> it would be a great idea. PSF probably would be still willing, but if 
> I recall correctly, that'd require a copyright assignment to PSF from 
> all contributors, and I still have painful memories about the Qt 
> contributor license agreement hassle... :-/

I'm almost 100% certain that the PSF hosting some resources for PySide 
won't come with a requirement about licensing or process for PySide.  Or 
at least that's my impression from having been on the PSF board some 
years ago, and from everything I've observed since. It certainly is true 
that a contributor agreement is needed for anything in Python itself and 
the Python standard library, but PySide would not go into the Python 
standard library.

That said, is the problem with Qt Project or a temporary one caused by 
the transfer from Nokia to Digia?

I don't care too much either way but maybe in the long term being part 
of the Qt Project will be less hassle (if really part of it, and not 
easily orphaned again as seems to have happened now).

- Stephan



From mairas at iki.fi  Fri Sep 28 14:22:38 2012
From: mairas at iki.fi (Matti Airas)
Date: Fri, 28 Sep 2012 15:22:38 +0300
Subject: [PySide] PySide website down
In-Reply-To: <506592EC.5070306@wingware.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
Message-ID: <CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>

Hi Stephan,

On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com> wrote:

> Matti Airas wrote:
>
>>

> I'm almost 100% certain that the PSF hosting some resources for PySide
> won't come with a requirement about licensing or process for PySide.  Or at
> least that's my impression from having been on the PSF board some years
> ago, and from everything I've observed since. It certainly is true that a
> contributor agreement is needed for anything in Python itself and the
> Python standard library, but PySide would not go into the Python standard
> library.
>

I was discussing the issue with some PSF board members back in August 2011,
and that was the message then.


> That said, is the problem with Qt Project or a temporary one caused by the
> transfer from Nokia to Digia?
>

It's probably really neither. I think the problem was more due to the
overworked Nokia Qt organization having to deliver to an unpublished closed
project, while at the same time having to cater for the open Qt Project.
The open project probably couldn't be sufficiently prioritized - it wasn't
an issue with Qt Project itself, IMHO. Ever an optimist, I actually think
Digia has more interest in Qt Project in general and in PySide too.

I got a while ago in contact with Lars Knoll (Qt lead maintainer), and he
wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia Qt
Commercial Director), and he wanted to resolve the issue without delay,
too. So, let's hope for the best.

I don't care too much either way but maybe in the long term being part of
> the Qt Project will be less hassle (if really part of it, and not easily
> orphaned again as seems to have happened now).


Me too, with the same condition. :-)

Cheers,

ma.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/a3b3d94d/attachment.html>

From hugo.lima at openbossa.org  Fri Sep 28 14:28:56 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Fri, 28 Sep 2012 09:28:56 -0300
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnsx4+6u70MOHHmdvjM4Rbe07tphiUJNj8hMMMS5RVcO1w@mail.gmail.com>
References: <CAAbtOZdy2TLgOzhfRWF0PAYwZf2oTEu05pS1j+kjUcndFC+xSQ@mail.gmail.com>
	<CAG_nbnu6KMPX-uj4_vs49N4Pj5p8Lfgcjp+uS_4zj9OL29xiyg@mail.gmail.com>
	<CAG_nbnsx4+6u70MOHHmdvjM4Rbe07tphiUJNj8hMMMS5RVcO1w@mail.gmail.com>
Message-ID: <2115111.g1d2iIWmVW@hugodesktop>

On Thursday, September 27, 2012 06:01:08 PM Srini Kommoori wrote:
> Here are temporary docs.
> 
> http://srinikom.github.com/pyside-docs/
> 
> . Search won't work as we are hosting them as static files.
> . Hope that is useful. I couldn't generate 1.1.2 docs so I just posted
> 1.0.7 from a local copy.

Hmmm... but the search is supposed to work offline, it's based on a javascript 
with no online queries.
 
> -Srini
> 
> On Thu, Sep 27, 2012 at 4:34 PM, Srini Kommoori <vasure at gmail.com> wrote:
> > Andrew, We hear you. We are doing everything we can. Worst case,
> > expect a temporary docs location by tomorrow.
> > 
> > -Srini
> > 
> > On Thu, Sep 27, 2012 at 3:32 PM, Andrew Nelson <andyfaff at gmail.com> wrote:
> >> Dear pysiders,
> >> 
> >>  I'm just getting started with PySide and Python. I really like this
> >> 
> >> binding for Qt. I appreciate the effort that is going into creating
> >> this code.
> >> 
> >> However, for a starter like me it's a real hurdle not having the
> >> website available for all the documentation, especially the class
> >> references. From the archive I know that work is going into getting
> >> the website transferred, I just wanted to say that I've got my fingers
> >> and toes crossed that it'll happen soon.
> >> 
> >> cheers,
> >> Andrew.
> >> 
> >> --
> >> _____________________________________
> >> Dr. Andrew Nelson
> >> 
> >> 
> >> _____________________________________
> >> _______________________________________________
> >> PySide mailing list
> >> PySide at qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/pyside
> 
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/274b988a/attachment.sig>

From vasure at gmail.com  Fri Sep 28 14:43:55 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Fri, 28 Sep 2012 05:43:55 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
	<CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
Message-ID: <CAG_nbntkmSWWA-Fr4wDqC3C-HCHYys9-MuGw4aVMjPn7kFntYQ@mail.gmail.com>

1. I contacted local Digia folks(Tuukka Ahoniemi) and they sent our
domain and vpc requests to concerned folks. Hope we will hear
something back from them today.

On the technical side of things, I just checked search also on the
docs, there is no dependency on a server as they are all static pages
and javascript is doing the search.
http://srinikom.github.com/pyside-docs/

So we could host docs on github without depending on anyone. All we
need is domain whois info access Or someone willing to modify domain
settings for us.

2. I can easily create a blogger site+blog with the same theme and we
all can collaborate and publish updates.

3. I volunteer to take up the hosting tasks going forward completely.
It would be good to know how is the project structured? Who posts
binaries? I think on the coding and checkin side, our git repository
is taken care right now - do we need any help on that?

Matti, Am I missing any hosting tasks?

thanks,
-Srini

On Fri, Sep 28, 2012 at 5:22 AM, Matti Airas <mairas at iki.fi> wrote:
> Hi Stephan,
>
> On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com> wrote:
>
>> Matti Airas wrote:
>
>
>>
>> I'm almost 100% certain that the PSF hosting some resources for PySide
>> won't come with a requirement about licensing or process for PySide.  Or at
>> least that's my impression from having been on the PSF board some years ago,
>> and from everything I've observed since. It certainly is true that a
>> contributor agreement is needed for anything in Python itself and the Python
>> standard library, but PySide would not go into the Python standard library.
>
>
> I was discussing the issue with some PSF board members back in August 2011,
> and that was the message then.
>
>>
>> That said, is the problem with Qt Project or a temporary one caused by the
>> transfer from Nokia to Digia?
>
>
> It's probably really neither. I think the problem was more due to the
> overworked Nokia Qt organization having to deliver to an unpublished closed
> project, while at the same time having to cater for the open Qt Project. The
> open project probably couldn't be sufficiently prioritized - it wasn't an
> issue with Qt Project itself, IMHO. Ever an optimist, I actually think Digia
> has more interest in Qt Project in general and in PySide too.
>
> I got a while ago in contact with Lars Knoll (Qt lead maintainer), and he
> wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia Qt
> Commercial Director), and he wanted to resolve the issue without delay, too.
> So, let's hope for the best.
>
>> I don't care too much either way but maybe in the long term being part of
>> the Qt Project will be less hassle (if really part of it, and not easily
>> orphaned again as seems to have happened now).
>
>
> Me too, with the same condition. :-)
>
> Cheers,
>
> ma.


From vasure at gmail.com  Fri Sep 28 14:44:44 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Fri, 28 Sep 2012 05:44:44 -0700
Subject: [PySide] PySide website down
In-Reply-To: <2115111.g1d2iIWmVW@hugodesktop>
References: <CAAbtOZdy2TLgOzhfRWF0PAYwZf2oTEu05pS1j+kjUcndFC+xSQ@mail.gmail.com>
	<CAG_nbnu6KMPX-uj4_vs49N4Pj5p8Lfgcjp+uS_4zj9OL29xiyg@mail.gmail.com>
	<CAG_nbnsx4+6u70MOHHmdvjM4Rbe07tphiUJNj8hMMMS5RVcO1w@mail.gmail.com>
	<2115111.g1d2iIWmVW@hugodesktop>
Message-ID: <CAG_nbnvN3obJfVXPdJCSKYz9FEb2mS8TSEgoznRJZpP97-GJMg@mail.gmail.com>

Hugo, You are right. Yea search works as well.

On Fri, Sep 28, 2012 at 5:28 AM, Hugo Parente Lima
<hugo.lima at openbossa.org> wrote:
> On Thursday, September 27, 2012 06:01:08 PM Srini Kommoori wrote:
>> Here are temporary docs.
>>
>> http://srinikom.github.com/pyside-docs/
>>
>> . Search won't work as we are hosting them as static files.
>> . Hope that is useful. I couldn't generate 1.1.2 docs so I just posted
>> 1.0.7 from a local copy.
>
> Hmmm... but the search is supposed to work offline, it's based on a javascript
> with no online queries.
>
>> -Srini
>>
>> On Thu, Sep 27, 2012 at 4:34 PM, Srini Kommoori <vasure at gmail.com> wrote:
>> > Andrew, We hear you. We are doing everything we can. Worst case,
>> > expect a temporary docs location by tomorrow.
>> >
>> > -Srini
>> >
>> > On Thu, Sep 27, 2012 at 3:32 PM, Andrew Nelson <andyfaff at gmail.com> wrote:
>> >> Dear pysiders,
>> >>
>> >>  I'm just getting started with PySide and Python. I really like this
>> >>
>> >> binding for Qt. I appreciate the effort that is going into creating
>> >> this code.
>> >>
>> >> However, for a starter like me it's a real hurdle not having the
>> >> website available for all the documentation, especially the class
>> >> references. From the archive I know that work is going into getting
>> >> the website transferred, I just wanted to say that I've got my fingers
>> >> and toes crossed that it'll happen soon.
>> >>
>> >> cheers,
>> >> Andrew.
>> >>
>> >> --
>> >> _____________________________________
>> >> Dr. Andrew Nelson
>> >>
>> >>
>> >> _____________________________________
>> >> _______________________________________________
>> >> PySide mailing list
>> >> PySide at qt-project.org
>> >> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside


From vasure at gmail.com  Fri Sep 28 15:46:46 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Fri, 28 Sep 2012 06:46:46 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbntkmSWWA-Fr4wDqC3C-HCHYys9-MuGw4aVMjPn7kFntYQ@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
	<CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
	<CAG_nbntkmSWWA-Fr4wDqC3C-HCHYys9-MuGw4aVMjPn7kFntYQ@mail.gmail.com>
Message-ID: <CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>

pyside.org redirect to wiki page is online. I have updated wiki with a
docs link.

Hugo, Is it possible to host static documentation pages on github
pyside account? I will send a pull request.

thanks,
-Srini

On Fri, Sep 28, 2012 at 5:43 AM, Srini Kommoori <vasure at gmail.com> wrote:
> 1. I contacted local Digia folks(Tuukka Ahoniemi) and they sent our
> domain and vpc requests to concerned folks. Hope we will hear
> something back from them today.
>
> On the technical side of things, I just checked search also on the
> docs, there is no dependency on a server as they are all static pages
> and javascript is doing the search.
> http://srinikom.github.com/pyside-docs/
>
> So we could host docs on github without depending on anyone. All we
> need is domain whois info access Or someone willing to modify domain
> settings for us.
>
> 2. I can easily create a blogger site+blog with the same theme and we
> all can collaborate and publish updates.
>
> 3. I volunteer to take up the hosting tasks going forward completely.
> It would be good to know how is the project structured? Who posts
> binaries? I think on the coding and checkin side, our git repository
> is taken care right now - do we need any help on that?
>
> Matti, Am I missing any hosting tasks?
>
> thanks,
> -Srini
>
> On Fri, Sep 28, 2012 at 5:22 AM, Matti Airas <mairas at iki.fi> wrote:
>> Hi Stephan,
>>
>> On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com> wrote:
>>
>>> Matti Airas wrote:
>>
>>
>>>
>>> I'm almost 100% certain that the PSF hosting some resources for PySide
>>> won't come with a requirement about licensing or process for PySide.  Or at
>>> least that's my impression from having been on the PSF board some years ago,
>>> and from everything I've observed since. It certainly is true that a
>>> contributor agreement is needed for anything in Python itself and the Python
>>> standard library, but PySide would not go into the Python standard library.
>>
>>
>> I was discussing the issue with some PSF board members back in August 2011,
>> and that was the message then.
>>
>>>
>>> That said, is the problem with Qt Project or a temporary one caused by the
>>> transfer from Nokia to Digia?
>>
>>
>> It's probably really neither. I think the problem was more due to the
>> overworked Nokia Qt organization having to deliver to an unpublished closed
>> project, while at the same time having to cater for the open Qt Project. The
>> open project probably couldn't be sufficiently prioritized - it wasn't an
>> issue with Qt Project itself, IMHO. Ever an optimist, I actually think Digia
>> has more interest in Qt Project in general and in PySide too.
>>
>> I got a while ago in contact with Lars Knoll (Qt lead maintainer), and he
>> wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia Qt
>> Commercial Director), and he wanted to resolve the issue without delay, too.
>> So, let's hope for the best.
>>
>>> I don't care too much either way but maybe in the long term being part of
>>> the Qt Project will be less hassle (if really part of it, and not easily
>>> orphaned again as seems to have happened now).
>>
>>
>> Me too, with the same condition. :-)
>>
>> Cheers,
>>
>> ma.


From mairas at iki.fi  Fri Sep 28 16:01:49 2012
From: mairas at iki.fi (Matti Airas)
Date: Fri, 28 Sep 2012 17:01:49 +0300
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
	<CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
	<CAG_nbntkmSWWA-Fr4wDqC3C-HCHYys9-MuGw4aVMjPn7kFntYQ@mail.gmail.com>
	<CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
Message-ID: <CAHfg+FPd3BMFvgJjg+6yaW2Q22O7prqew3rmZfhRmRC52_Z4jg@mail.gmail.com>

If we can get easy access to static web area hosted by Qt Project
Foundation, I think that would be much preferable solution.

I'm thinking of having a link to PySide documentation at
http://qt-project.org/doc/. :-)

ma.

On 28 September 2012 16:46, Srini Kommoori <vasure at gmail.com> wrote:

> pyside.org redirect to wiki page is online. I have updated wiki with a
> docs link.
>
> Hugo, Is it possible to host static documentation pages on github
> pyside account? I will send a pull request.
>
> thanks,
> -Srini
>
> On Fri, Sep 28, 2012 at 5:43 AM, Srini Kommoori <vasure at gmail.com> wrote:
> > 1. I contacted local Digia folks(Tuukka Ahoniemi) and they sent our
> > domain and vpc requests to concerned folks. Hope we will hear
> > something back from them today.
> >
> > On the technical side of things, I just checked search also on the
> > docs, there is no dependency on a server as they are all static pages
> > and javascript is doing the search.
> > http://srinikom.github.com/pyside-docs/
> >
> > So we could host docs on github without depending on anyone. All we
> > need is domain whois info access Or someone willing to modify domain
> > settings for us.
> >
> > 2. I can easily create a blogger site+blog with the same theme and we
> > all can collaborate and publish updates.
> >
> > 3. I volunteer to take up the hosting tasks going forward completely.
> > It would be good to know how is the project structured? Who posts
> > binaries? I think on the coding and checkin side, our git repository
> > is taken care right now - do we need any help on that?
> >
> > Matti, Am I missing any hosting tasks?
> >
> > thanks,
> > -Srini
> >
> > On Fri, Sep 28, 2012 at 5:22 AM, Matti Airas <mairas at iki.fi> wrote:
> >> Hi Stephan,
> >>
> >> On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com>
> wrote:
> >>
> >>> Matti Airas wrote:
> >>
> >>
> >>>
> >>> I'm almost 100% certain that the PSF hosting some resources for PySide
> >>> won't come with a requirement about licensing or process for PySide.
>  Or at
> >>> least that's my impression from having been on the PSF board some
> years ago,
> >>> and from everything I've observed since. It certainly is true that a
> >>> contributor agreement is needed for anything in Python itself and the
> Python
> >>> standard library, but PySide would not go into the Python standard
> library.
> >>
> >>
> >> I was discussing the issue with some PSF board members back in August
> 2011,
> >> and that was the message then.
> >>
> >>>
> >>> That said, is the problem with Qt Project or a temporary one caused by
> the
> >>> transfer from Nokia to Digia?
> >>
> >>
> >> It's probably really neither. I think the problem was more due to the
> >> overworked Nokia Qt organization having to deliver to an unpublished
> closed
> >> project, while at the same time having to cater for the open Qt
> Project. The
> >> open project probably couldn't be sufficiently prioritized - it wasn't
> an
> >> issue with Qt Project itself, IMHO. Ever an optimist, I actually think
> Digia
> >> has more interest in Qt Project in general and in PySide too.
> >>
> >> I got a while ago in contact with Lars Knoll (Qt lead maintainer), and
> he
> >> wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia
> Qt
> >> Commercial Director), and he wanted to resolve the issue without delay,
> too.
> >> So, let's hope for the best.
> >>
> >>> I don't care too much either way but maybe in the long term being part
> of
> >>> the Qt Project will be less hassle (if really part of it, and not
> easily
> >>> orphaned again as seems to have happened now).
> >>
> >>
> >> Me too, with the same condition. :-)
> >>
> >> Cheers,
> >>
> >> ma.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/8cfff601/attachment.html>

From hugo.lima at openbossa.org  Fri Sep 28 16:02:44 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Fri, 28 Sep 2012 11:02:44 -0300
Subject: [PySide] PySide website down
In-Reply-To: <CAHfg+FPd3BMFvgJjg+6yaW2Q22O7prqew3rmZfhRmRC52_Z4jg@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
	<CAHfg+FPd3BMFvgJjg+6yaW2Q22O7prqew3rmZfhRmRC52_Z4jg@mail.gmail.com>
Message-ID: <4636142.at1aPHNbS3@hugodesktop>

On Friday, September 28, 2012 05:01:49 PM Matti Airas wrote:
> If we can get easy access to static web area hosted by Qt Project
> Foundation, I think that would be much preferable solution.

I agree.
 
> I'm thinking of having a link to PySide documentation at
> http://qt-project.org/doc/. :-)

This would be really nice.
 
> ma.
> 
> On 28 September 2012 16:46, Srini Kommoori <vasure at gmail.com> wrote:
> > pyside.org redirect to wiki page is online. I have updated wiki with a
> > docs link.
> > 
> > Hugo, Is it possible to host static documentation pages on github
> > pyside account? I will send a pull request.
> > 
> > thanks,
> > -Srini
> > 
> > On Fri, Sep 28, 2012 at 5:43 AM, Srini Kommoori <vasure at gmail.com> wrote:
> > > 1. I contacted local Digia folks(Tuukka Ahoniemi) and they sent our
> > > domain and vpc requests to concerned folks. Hope we will hear
> > > something back from them today.
> > > 
> > > On the technical side of things, I just checked search also on the
> > > docs, there is no dependency on a server as they are all static pages
> > > and javascript is doing the search.
> > > http://srinikom.github.com/pyside-docs/
> > > 
> > > So we could host docs on github without depending on anyone. All we
> > > need is domain whois info access Or someone willing to modify domain
> > > settings for us.
> > > 
> > > 2. I can easily create a blogger site+blog with the same theme and we
> > > all can collaborate and publish updates.
> > > 
> > > 3. I volunteer to take up the hosting tasks going forward completely.
> > > It would be good to know how is the project structured? Who posts
> > > binaries? I think on the coding and checkin side, our git repository
> > > is taken care right now - do we need any help on that?
> > > 
> > > Matti, Am I missing any hosting tasks?
> > > 
> > > thanks,
> > > -Srini
> > > 
> > > On Fri, Sep 28, 2012 at 5:22 AM, Matti Airas <mairas at iki.fi> wrote:
> > >> Hi Stephan,
> > >> 
> > >> On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com>
> > 
> > wrote:
> > >>> Matti Airas wrote:
> > >>> 
> > >>> 
> > >>> 
> > >>> I'm almost 100% certain that the PSF hosting some resources for PySide
> > >>> won't come with a requirement about licensing or process for PySide.
> >  
> >  Or at
> >  
> > >>> least that's my impression from having been on the PSF board some
> > 
> > years ago,
> > 
> > >>> and from everything I've observed since. It certainly is true that a
> > >>> contributor agreement is needed for anything in Python itself and the
> > 
> > Python
> > 
> > >>> standard library, but PySide would not go into the Python standard
> > 
> > library.
> > 
> > >> I was discussing the issue with some PSF board members back in August
> > 
> > 2011,
> > 
> > >> and that was the message then.
> > >> 
> > >>> That said, is the problem with Qt Project or a temporary one caused by
> > 
> > the
> > 
> > >>> transfer from Nokia to Digia?
> > >> 
> > >> It's probably really neither. I think the problem was more due to the
> > >> overworked Nokia Qt organization having to deliver to an unpublished
> > 
> > closed
> > 
> > >> project, while at the same time having to cater for the open Qt
> > 
> > Project. The
> > 
> > >> open project probably couldn't be sufficiently prioritized - it wasn't
> > 
> > an
> > 
> > >> issue with Qt Project itself, IMHO. Ever an optimist, I actually think
> > 
> > Digia
> > 
> > >> has more interest in Qt Project in general and in PySide too.
> > >> 
> > >> I got a while ago in contact with Lars Knoll (Qt lead maintainer), and
> > 
> > he
> > 
> > >> wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia
> > 
> > Qt
> > 
> > >> Commercial Director), and he wanted to resolve the issue without delay,
> > 
> > too.
> > 
> > >> So, let's hope for the best.
> > >> 
> > >>> I don't care too much either way but maybe in the long term being part
> > 
> > of
> > 
> > >>> the Qt Project will be less hassle (if really part of it, and not
> > 
> > easily
> > 
> > >>> orphaned again as seems to have happened now).
> > >> 
> > >> Me too, with the same condition. :-)
> > >> 
> > >> Cheers,
> > >> 
> > >> ma.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/7ba451f1/attachment.sig>

From vasure at gmail.com  Fri Sep 28 16:08:25 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Fri, 28 Sep 2012 07:08:25 -0700
Subject: [PySide] PySide website down
In-Reply-To: <4636142.at1aPHNbS3@hugodesktop>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
	<CAHfg+FPd3BMFvgJjg+6yaW2Q22O7prqew3rmZfhRmRC52_Z4jg@mail.gmail.com>
	<4636142.at1aPHNbS3@hugodesktop>
Message-ID: <CAG_nbnt0RgbjUfpTX8+cawddAbuG9nQjqLDjiW5bdL40crP3ig@mail.gmail.com>

Yea. Hosting on qt-project.org sounds good.

On Fri, Sep 28, 2012 at 7:02 AM, Hugo Parente Lima
<hugo.lima at openbossa.org> wrote:
> On Friday, September 28, 2012 05:01:49 PM Matti Airas wrote:
>> If we can get easy access to static web area hosted by Qt Project
>> Foundation, I think that would be much preferable solution.
>
> I agree.
>
>> I'm thinking of having a link to PySide documentation at
>> http://qt-project.org/doc/. :-)
>
> This would be really nice.
>
>> ma.
>>
>> On 28 September 2012 16:46, Srini Kommoori <vasure at gmail.com> wrote:
>> > pyside.org redirect to wiki page is online. I have updated wiki with a
>> > docs link.
>> >
>> > Hugo, Is it possible to host static documentation pages on github
>> > pyside account? I will send a pull request.
>> >
>> > thanks,
>> > -Srini
>> >
>> > On Fri, Sep 28, 2012 at 5:43 AM, Srini Kommoori <vasure at gmail.com> wrote:
>> > > 1. I contacted local Digia folks(Tuukka Ahoniemi) and they sent our
>> > > domain and vpc requests to concerned folks. Hope we will hear
>> > > something back from them today.
>> > >
>> > > On the technical side of things, I just checked search also on the
>> > > docs, there is no dependency on a server as they are all static pages
>> > > and javascript is doing the search.
>> > > http://srinikom.github.com/pyside-docs/
>> > >
>> > > So we could host docs on github without depending on anyone. All we
>> > > need is domain whois info access Or someone willing to modify domain
>> > > settings for us.
>> > >
>> > > 2. I can easily create a blogger site+blog with the same theme and we
>> > > all can collaborate and publish updates.
>> > >
>> > > 3. I volunteer to take up the hosting tasks going forward completely.
>> > > It would be good to know how is the project structured? Who posts
>> > > binaries? I think on the coding and checkin side, our git repository
>> > > is taken care right now - do we need any help on that?
>> > >
>> > > Matti, Am I missing any hosting tasks?
>> > >
>> > > thanks,
>> > > -Srini
>> > >
>> > > On Fri, Sep 28, 2012 at 5:22 AM, Matti Airas <mairas at iki.fi> wrote:
>> > >> Hi Stephan,
>> > >>
>> > >> On 28 September 2012 15:07, Stephan Deibel <sdeibel at wingware.com>
>> >
>> > wrote:
>> > >>> Matti Airas wrote:
>> > >>>
>> > >>>
>> > >>>
>> > >>> I'm almost 100% certain that the PSF hosting some resources for PySide
>> > >>> won't come with a requirement about licensing or process for PySide.
>> >
>> >  Or at
>> >
>> > >>> least that's my impression from having been on the PSF board some
>> >
>> > years ago,
>> >
>> > >>> and from everything I've observed since. It certainly is true that a
>> > >>> contributor agreement is needed for anything in Python itself and the
>> >
>> > Python
>> >
>> > >>> standard library, but PySide would not go into the Python standard
>> >
>> > library.
>> >
>> > >> I was discussing the issue with some PSF board members back in August
>> >
>> > 2011,
>> >
>> > >> and that was the message then.
>> > >>
>> > >>> That said, is the problem with Qt Project or a temporary one caused by
>> >
>> > the
>> >
>> > >>> transfer from Nokia to Digia?
>> > >>
>> > >> It's probably really neither. I think the problem was more due to the
>> > >> overworked Nokia Qt organization having to deliver to an unpublished
>> >
>> > closed
>> >
>> > >> project, while at the same time having to cater for the open Qt
>> >
>> > Project. The
>> >
>> > >> open project probably couldn't be sufficiently prioritized - it wasn't
>> >
>> > an
>> >
>> > >> issue with Qt Project itself, IMHO. Ever an optimist, I actually think
>> >
>> > Digia
>> >
>> > >> has more interest in Qt Project in general and in PySide too.
>> > >>
>> > >> I got a while ago in contact with Lars Knoll (Qt lead maintainer), and
>> >
>> > he
>> >
>> > >> wanted to resolve the issue ASAP. Also talked to Tuukka Turunen (Digia
>> >
>> > Qt
>> >
>> > >> Commercial Director), and he wanted to resolve the issue without delay,
>> >
>> > too.
>> >
>> > >> So, let's hope for the best.
>> > >>
>> > >>> I don't care too much either way but maybe in the long term being part
>> >
>> > of
>> >
>> > >>> the Qt Project will be less hassle (if really part of it, and not
>> >
>> > easily
>> >
>> > >>> orphaned again as seems to have happened now).
>> > >>
>> > >> Me too, with the same condition. :-)
>> > >>
>> > >> Cheers,
>> > >>
>> > >> ma.


From sdeibel at wingware.com  Fri Sep 28 16:14:09 2012
From: sdeibel at wingware.com (Stephan Deibel)
Date: Fri, 28 Sep 2012 10:14:09 -0400
Subject: [PySide] PySide website down
In-Reply-To: <CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
	<CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
Message-ID: <5065B0B1.8020201@wingware.com>

Matti Airas wrote:
>
>     I'm almost 100% certain that the PSF hosting some resources for
>     PySide won't come with a requirement about licensing or process
>     for PySide.  Or at least that's my impression from having been on
>     the PSF board some years ago, and from everything I've observed
>     since. It certainly is true that a contributor agreement is needed
>     for anything in Python itself and the Python standard library, but
>     PySide would not go into the Python standard library.
>
>
> I was discussing the issue with some PSF board members back in August 
> 2011, and that was the message then.

I just contacted the PSF board directly and indeed that seems to be the 
case if the PSF were to take over ownership of PySide.  That isn't what 
I thought was on the table -- I thought it was just to get some PSF 
resources for hosting the project's website/etc.  But the snippets of 
past emails that were forwarded to me clearly were talking about 
contributing the intellectual property rights to PySide to the PSF, so 
it would also become responsible for defending any lawsuits, dealing 
with abuse of the trademark, etc.  That isn't really possible w/o 
contributor agreements.

Sorry, I just thought we were talking about a hosting/funding-of-hosting 
arrangement here.  I personally don't think the PSF should take on 
owning/defending more than Python and the Python standard library, and 
it didn't occur to me that they would even consider that.

Anyway, this is probably a moot point but I figured I'd post this for 
the record.

- Stephan



From anderson.lizardo at openbossa.org  Fri Sep 28 17:51:21 2012
From: anderson.lizardo at openbossa.org (Anderson Lizardo)
Date: Fri, 28 Sep 2012 11:51:21 -0400
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
	<CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
	<CAG_nbntkmSWWA-Fr4wDqC3C-HCHYys9-MuGw4aVMjPn7kFntYQ@mail.gmail.com>
	<CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
Message-ID: <CAJdJm_P__qx-voexmu3hEhoJYf4qNkKFZn0Azwvf4pK-JZYrXA@mail.gmail.com>

Hi Srini,

On Fri, Sep 28, 2012 at 9:46 AM, Srini Kommoori <vasure at gmail.com> wrote:
> pyside.org redirect to wiki page is online. I have updated wiki with a
> docs link.
>
> Hugo, Is it possible to host static documentation pages on github
> pyside account? I will send a pull request.

First of all, many thanks for helping taking care of this!

Second, we should not forget the tarball downloads (whose links listed
in http://qt-project.org/wiki/PySideDownloads are currently broken).
Can we have those hosted in github.com as well (under PySide account)?
If I remember correctly, they have a place to store source tarballs as
well.

This way, we have the full infrastructure up at least while a
qt-project.org hosting space is not provided.

PS: Did anyone got access to the old virtual image? It would be nice
to backup all previous tarball releases, and upload them to some place
(PySide github.com account, or qt-project.org in the future).

Best Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil


From vasure at gmail.com  Fri Sep 28 21:37:59 2012
From: vasure at gmail.com (Srini Kommoori)
Date: Fri, 28 Sep 2012 12:37:59 -0700
Subject: [PySide] PySide website down
In-Reply-To: <CAJdJm_P__qx-voexmu3hEhoJYf4qNkKFZn0Azwvf4pK-JZYrXA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_M1Q3t_K-32+MX5v1QbT8he4a-DKV5yTieBopX6C9UtLw@mail.gmail.com>
	<CACBMVRhJw_ZpNN101Ak4K+9zeR3pC3jhWMN6o49qLDcTOCFnqA@mail.gmail.com>
	<CAHC6v6hof3-cJtCBMYtHMQMXDa5TusiCTCrKEJOMG+T7pPvRaA@mail.gmail.com>
	<CAG_nbnutQ6L2w+h_Cu8cfhs=DDhDdcr28Jmky46czF9cWKnuFA@mail.gmail.com>
	<CAHfg+FPJUkGPEioBSguWRcGO4U23=jxaQ5At5gwQ+ui_GMth1A@mail.gmail.com>
	<506592EC.5070306@wingware.com>
	<CAHfg+FMwZ8exnK7kvyKjD0BfODu9zdXcH61S+TJ8T9ThJUHbEA@mail.gmail.com>
	<CAG_nbntkmSWWA-Fr4wDqC3C-HCHYys9-MuGw4aVMjPn7kFntYQ@mail.gmail.com>
	<CAG_nbnteVrg6UcooRYxjb+YkzQ1t5qBJ4Hwiq3hwPBv7tyOjFA@mail.gmail.com>
	<CAJdJm_P__qx-voexmu3hEhoJYf4qNkKFZn0Azwvf4pK-JZYrXA@mail.gmail.com>
Message-ID: <CAG_nbnvf-EmDDZpR8S1mVh-Ft0mJRe2KexFc7KfV90HQh6W9TA@mail.gmail.com>

Current setup pyside.org redirect to qt-project.org/wiki/PySide. This
works well and we will continue until further notice.

I think we need to decide on the final destination for PySide docs. We
discussed few months ago but didn't finalize and we just left the
topic. People who are trying to help us are getting confused about
what is that we want at the end.

Here are proposals for PySide Docs:
==========================
Option #1. Final destination on qt-project.org (retire pyside.org and
continue the redirect)
    * Wiki as the landing page
    * Need git/hg access to upload docs to qt-project.org to push
static file hosting [unknown]

Option #2. Final destination on qt-project.org (retire pyside.org and
continue the redirect)
    * Wiki as the landing page
    * link docs to pyside.github.com/pyside-docs/

Option #3. Final destination on pyside.org (some thing like
http://www.pyside.org/docs/ )
    * github static pages with domain name mapped to pyside.org

Let's finalize among above 3 and we can work towards that.

thanks,
-Srini

On Fri, Sep 28, 2012 at 8:51 AM, Anderson Lizardo
<anderson.lizardo at openbossa.org> wrote:
> Hi Srini,
>
> On Fri, Sep 28, 2012 at 9:46 AM, Srini Kommoori <vasure at gmail.com> wrote:
>> pyside.org redirect to wiki page is online. I have updated wiki with a
>> docs link.
>>
>> Hugo, Is it possible to host static documentation pages on github
>> pyside account? I will send a pull request.
>
> First of all, many thanks for helping taking care of this!
>
> Second, we should not forget the tarball downloads (whose links listed
> in http://qt-project.org/wiki/PySideDownloads are currently broken).
> Can we have those hosted in github.com as well (under PySide account)?
> If I remember correctly, they have a place to store source tarballs as
> well.
>
> This way, we have the full infrastructure up at least while a
> qt-project.org hosting space is not provided.
>
> PS: Did anyone got access to the old virtual image? It would be nice
> to backup all previous tarball releases, and upload them to some place
> (PySide github.com account, or qt-project.org in the future).
>
> Best Regards,
> --
> Anderson Lizardo
> Instituto Nokia de Tecnologia - INdT
> Manaus - Brazil


From hugo.lima at openbossa.org  Fri Sep 28 22:04:49 2012
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Fri, 28 Sep 2012 17:04:49 -0300
Subject: [PySide] PySide website down
In-Reply-To: <CAG_nbnvf-EmDDZpR8S1mVh-Ft0mJRe2KexFc7KfV90HQh6W9TA@mail.gmail.com>
References: <2741920.NSFmnYkgdy@hugodesktop>
	<CAJdJm_P__qx-voexmu3hEhoJYf4qNkKFZn0Azwvf4pK-JZYrXA@mail.gmail.com>
	<CAG_nbnvf-EmDDZpR8S1mVh-Ft0mJRe2KexFc7KfV90HQh6W9TA@mail.gmail.com>
Message-ID: <6813387.X7LCjeq48t@hugodesktop>

On Friday, September 28, 2012 12:37:59 PM Srini Kommoori wrote:
> Current setup pyside.org redirect to qt-project.org/wiki/PySide. This
> works well and we will continue until further notice.
> 
> I think we need to decide on the final destination for PySide docs. We
> discussed few months ago but didn't finalize and we just left the
> topic. People who are trying to help us are getting confused about
> what is that we want at the end.

I like the current situation of the use the wiki as website, better a up to 
date ugly wiki than a beautiful website outdated.

Let's wait a bit to see if the docs can go into qt-projects, if not, we can 
put them as github static pages.
 
> Here are proposals for PySide Docs:
> ==========================
> Option #1. Final destination on qt-project.org (retire pyside.org and
> continue the redirect)
>     * Wiki as the landing page
>     * Need git/hg access to upload docs to qt-project.org to push
> static file hosting [unknown]
> 
> Option #2. Final destination on qt-project.org (retire pyside.org and
> continue the redirect)
>     * Wiki as the landing page
>     * link docs to pyside.github.com/pyside-docs/
> 
> Option #3. Final destination on pyside.org (some thing like
> http://www.pyside.org/docs/ )
>     * github static pages with domain name mapped to pyside.org
> 
> Let's finalize among above 3 and we can work towards that.
> 
> thanks,
> -Srini
> 
> On Fri, Sep 28, 2012 at 8:51 AM, Anderson Lizardo
> 
> <anderson.lizardo at openbossa.org> wrote:
> > Hi Srini,
> > 
> > On Fri, Sep 28, 2012 at 9:46 AM, Srini Kommoori <vasure at gmail.com> wrote:
> >> pyside.org redirect to wiki page is online. I have updated wiki with a
> >> docs link.
> >> 
> >> Hugo, Is it possible to host static documentation pages on github
> >> pyside account? I will send a pull request.
> > 
> > First of all, many thanks for helping taking care of this!
> > 
> > Second, we should not forget the tarball downloads (whose links listed
> > in http://qt-project.org/wiki/PySideDownloads are currently broken).
> > Can we have those hosted in github.com as well (under PySide account)?
> > If I remember correctly, they have a place to store source tarballs as
> > well.
> > 
> > This way, we have the full infrastructure up at least while a
> > qt-project.org hosting space is not provided.
> > 
> > PS: Did anyone got access to the old virtual image? It would be nice
> > to backup all previous tarball releases, and upload them to some place
> > (PySide github.com account, or qt-project.org in the future).
> > 
> > Best Regards,
> > --
> > Anderson Lizardo
> > Instituto Nokia de Tecnologia - INdT
> > Manaus - Brazil
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20120928/7b859b4d/attachment.sig>