the latest ebuild in the repositories is for 2.3.9, several versions were released since then, including a major change to version 3 with many improvements and better support for python3. latest release is 3.0.2, it would be great to have an up-to-date ebuild.
https://github.com/spyder-ide/spyder/releases
*** Bug 565856 has been marked as a duplicate of this bug. ***
commit e2f891011f3883c81282af06d0cbf522f8c71040 Author: Andrey Grozin <grozin@gentoo.org> Date: Mon Dec 12 21:34:30 2016 +0700 dev-python/spyder: bump to 3.0.2 Bug: 602242 Package-Manager: portage-2.3.3 commit 1cc54d76539ea27219f5639b72162b7adb77e309 Author: Andrey Grozin <grozin@gentoo.org> Date: Mon Dec 12 21:27:37 2016 +0700 dev-python/qtawesome: initial import Package-Manager: portage-2.3.3 commit 48d47927ff2c30cbf4ce308c81b73ce3be1ced81 Author: Andrey Grozin <grozin@gentoo.org> Date: Mon Dec 12 21:30:12 2016 +0700 dev-python/rope_py3k: initial import Package-Manager: portage-2.3.3
wow, that was fast! it works great, thank you. there seems to be something wrong with the patch, though. applying the patch, only the version for python3 is installed, while skipping the patch both versions for python3 and python2 are installed, with two scripts: spyder, pointing to /usr/lib/python-exec/python2.7/spyder, and spyder3, pointing to /usr/lib/python-exec/python3.5/spyder3. for now i modified the ebuild to skip the patch, although that brings other problems. but at least i have both versions working.
(In reply to edes from comment #4) > applying the patch, only the version for python3 is installed, while > skipping the patch both versions for python3 and python2 are installed, with > two scripts: spyder, pointing to /usr/lib/python-exec/python2.7/spyder, and > spyder3, pointing to /usr/lib/python-exec/python3.5/spyder3. If you eselect python-2.7 and start spyder, the python-2.7 version is started; if you eselect python-3.x, the python-3.x version is started. This is the standard Gentoo behaviour: if a python package installs some script[s], it[they] is[are] started with the currently eselected python.
(In reply to Andrey Grozin from comment #5) > If you eselect python-2.7 and start spyder, the python-2.7 version is > started; if you eselect python-3.x, the python-3.x version is started. This > is the standard Gentoo behaviour: this seems to be not only very cumbersome and unnecessary but also inconvenient, since the eselect command must be run by root and changes the python environment system-wide. on the other hand, i don't see how this is "the standard Gentoo behaviour". the ipython package installed by the ebuild, for example, includes different scripts to launch versions 2 and 3 without having to eselect the python environment, which i find only logical. it seems to me that spyder should follow the same rationale (as is the default spyder installation, by the way). thanks for your attention.
to elaborate this a bit further, i think that ideally spyder should follow the same criterion as ipython and other python packages, where for example ipython2 and ipython3 launch versions 2 and 3 respectively, and ipython launches whatever version is set system-wide by eselect. or at least leave spyder for python2 and spyder3 for python3, as is the default installation.
(In reply to edes from comment #7) > to elaborate this a bit further, i think that ideally spyder should follow > the same criterion as ipython and other python packages, where for example > ipython2 and ipython3 launch versions 2 and 3 respectively, and ipython > launches whatever version is set system-wide by eselect. and this is exactly what the new 3.0.2-r1 version does!! that's great, thank you!!
