Bug 33 – PySide packages are only compiled against one python version

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 33 - PySide packages are only compiled against one python version

Summary:

PySide packages are only compiled against one python version

Status:	CLOSED WONTFIX

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	HEAD
Platform:	All All

Importance:	P5 normal
Assigned To:	Lauro Moura

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-04 09:20 EEST by Matti Airas
Modified:	2009-11-24 15:36 EET (History)
CC List:	6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matti Airas 2009-09-04 09:20:12 EEST

As reported on the IRC:

<OdyX> And finally (just before lunch :-p ) I have a larger issue : all pyside*
things are only compiled against one python version
<OdyX> where we (as in "Debian") expect to get modules et'al compiled for all
python versions available

[...]

<OdyX>  [16:46:00] <POX> -dbg package should provide .so files for all
supported Python versions
<OdyX> [jeudi 3 septembre 2009] [16:46:09] <POX> same for "normal" package
<OdyX> mairas: from what I can see/understand, the root CMakeLists only looks
for one python version
<mairas> ah
<OdyX> (you might be interested in coming discuss this with our specialists in
#debian-python on OFTC (irc.debian.org)
<OdyX> [nobody's answering now, but still :-p ]

Comment 1 Hugo Parente Lima 2009-09-04 14:55:13 EEST

Why not compile pyside for each python version and them create one package for
each version?

Comment 2 Anderson Lizardo 2009-09-15 15:49:57 EEST

Clarification: the PPA packages are experimental and for "technology preview"
purposes. OdyX is already working on properly packaging for Debian, and we will
reuse it for our snapshot packages once it is finished.

Therefore, I suggest marking this bug as WONTFIX; it will be fixed anyway by
the new packaging.

Comment 3 Lauro Moura 2009-10-26 16:39:42 EET

Actually this is a limitation in CMake. Their FindPython*.cmake modules always
search for the newest python.

Following Lizardo's advice, marking as WONTFIX.