Bug 487860 – dev-python/pyside-tools: python3.3 is restricted for some reason

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pacho Ramos 2013-10-13 09:51:52 UTC]

But I cannot find any reference to any problem:
  19 Oct 2012; Patrick Lauer <[e-mail]> pyside-tools-0.2.14.ebuild:
  Restricting python 3.3

[Comment 1 Rafał Mużyło 2013-10-13 10:47:07 UTC]

Well, it's both simple and complicated.
See bug 477844 where I've described the problem.

The short of it is that pyside status in regard to python 3.3 - aside of needing patches to be built - is as of 1.2.0 unknown.

[Comment 2 Pacho Ramos 2013-10-13 10:59:42 UTC]

I see instructions for python-3.3 *on windows* at:
"Install Qt 4.8 libraries for Windows VS 2008 edition when building against Python 2.6, 2.7 or 3.2. Install Qt 4.8 libraries for Windows VS 2010 edition when building against Python 3.3."

https://pypi.python.org/pypi/PySide

If you have some patches adding 3.3 support, please show them :)

Thanks

[Comment 3 Rafał Mużyło 2013-10-13 13:32:37 UTC]

Other than the sed lines, I've mentioned in bug 477844, I can't really tell if anything else is necessary - that's why I'm saying the status is unknown.

[Comment 4 Rafał Mużyło 2013-10-13 13:34:18 UTC]

Note also the remark in the first comment there.

[Comment 5 Pacho Ramos 2013-10-13 13:37:31 UTC]

But I don't see their equivalent in pyside-tools sources :(

[Comment 6 Rafał Mużyło 2013-10-13 15:05:56 UTC]

(In reply to Pacho Ramos from comment #5)
> But I don't see their equivalent in pyside-tools sources :(

Cause there isn't any.
As long as you add those lines to shiboken ebuild, the descendant ebuilds need only the new value in PYTHON_COMPAT or removing it from RESTRICT_PYTHON_ABIS.

Barring the mentioned remark, that is.

[Comment 7 Davide Pesavento 2013-10-20 23:16:04 UTC]

Assigning to qt@ rather than some random herd...

[Comment 8 Helmut Jarausch 2013-11-14 08:53:35 UTC]

This is probably the same bug.
The complete build log for pyside-tools-0.2.15 is :

 * Package:    dev-python/pyside-tools-0.2.15
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   preserve-libs sandbox splitdebug userpriv usersandbox
>>> [1m[37mcfg-update-1.8.2-r1[0m[0m: Creating checksum index...
 * ERROR: dev-python/pyside-tools-0.2.15::gentoo failed (setup phase):
 *   Active version of CPython 3 is not supported by dev-python/pyside-tools-0.2.15
 * 
 * Call stack:
 *       ebuild.sh, line  93:  Called pkg_setup
 *       ebuild.sh, line 317:  Called python_pkg_setup
 *   python.eclass, line 430:  Called _python_calculate_PYTHON_ABIS
 *   python.eclass, line 842:  Called die
 * The specific snippet of code:
 *   						die "Active version of CPython 3 is not supported by ${CATEGORY}/${PF}"
 * 


eselect python list
Available Python interpreters:
  [1]   python2.7 *
  [2]   python3.3
  [3]   python3.4

[Comment 9 George L. Emigh 2013-12-03 19:19:04 UTC]

Having the same problem, is there a workaround available till this gets fixed?
 
 * Package:    dev-python/pyside-tools-0.2.15
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux multilib policykit userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * ERROR: dev-python/pyside-tools-0.2.15::gentoo failed (setup phase):
 *   Active version of CPython 3 is not supported by dev-python/pyside-tools-0.2.15
 * 
 * Call stack:
 *       ebuild.sh, line  93:  Called pkg_setup
 *       ebuild.sh, line 317:  Called python_pkg_setup
 *   python.eclass, line 430:  Called _python_calculate_PYTHON_ABIS
 *   python.eclass, line 842:  Called die
 * The specific snippet of code:
 *                                              die "Active version of CPython 3 is not supported by ${CATEGORY}/${PF}"

# eselect python list
Available Python interpreters:
  [1]   python2.7 *
  [2]   python3.3

[Comment 10 Justin Lecher (RETIRED) 2013-12-12 13:12:08 UTC]

IS here a real bug which stops us from adding 3_3?

[Comment 11 Michael Palimaka (kensington) 2013-12-12 13:42:42 UTC]

(In reply to Justin Lecher from comment #10)
> IS here a real bug which stops us from adding 3_3?

See bug #477844, the issue is that upstream does not support 3.3 natively, and we have to patch the build system to enable it.

We would prefer to have the issue raised upstream first.

[Comment 12 Rafał Mużyło 2013-12-12 16:13:25 UTC]

Again, as noted in bug 477844, upstream has been informed about this problem https://bugreports.qt-project.org/browse/PYSIDE-157), but doesn't seem be doing anything about it, so it's hard to tell whether the problem lies just in a badly written macro (that is one, that needs an update with every upstream release, like - for example - FindBoost.cmake (though that one at least has an override var)) or in something more.

[Comment 13 Davide Pesavento 2013-12-19 23:31:04 UTC]

BTW pyside-tools needs to be ported to python-r1 too.

[Comment 14 Davide Pesavento 2013-12-26 02:01:45 UTC]

  26 Dec 2013; Davide Pesavento <[e-mail]> pyside-tools-0.2.15.ebuild:
  Unrestrict python 3.3

Please give it a try and report back.

[Comment 15 Pacho Ramos 2013-12-26 10:02:49 UTC]

Well, I am unsure about how to test it since looks like its tests are disabled :(, if you want me to follow some steps to test, please let me know :)

[Comment 16 Tolga Dalman 2014-07-06 18:13:19 UTC]

The issue seems to be resolved with 1.2.2, though the referenced upstream ticket is not yet closed.

[Comment 17 Davide Pesavento 2014-07-06 20:05:58 UTC]

(In reply to Tolga Dalman from comment #16)
> The issue seems to be resolved with 1.2.2, though the referenced upstream
> ticket is not yet closed.

Well, I'm closing then... please reopen if python3.3 causes any problems.