spyder 2.3.0 is now available at https://bitbucket.org/spyder-ide/spyderlib/downloads Reproducible: Always
This creates a major problem. The upstream makers of rope, and dep to spyder, instead of having py3 support added to the current rope, instead has a separate package and repo, rope_py3k, which makes an identical set of modules under rope, making for the perfect file collisions crash. This will take a while to figure.
What does it mean? Which steps could be taken to create spyder ebuild without making so much mess with rope?
(In reply to michal.halenka from comment #2) > What does it mean? Which steps could be taken to create spyder ebuild > without making so much mess with rope? simple. bump spyder without py3 support
(In reply to Ian Delaney from comment #3) > simple. bump spyder without py3 support well, I wanted spyder to develop in py3 so thats not an option for me :-(
Me too !
well, it can be done by use of slotting, however, unless someone can figure out and present how not to, the installed spyder could be either py2 or py3 capable. Although awkward, it still makes the bumping of spyder with both viable. To date no-one has offered the above required solution.
I'm afraid the main issues is that rope_py3k is a fork that is no longer maintained. Look at rope git [1] vs rope_py3k hg [2]. [1]:https://github.com/python-rope/rope/commits/master [2]:https://bitbucket.org/agr/rope_py3k/commits/all
(In reply to Michał Górny from comment #7) > I'm afraid the main issues is that rope_py3k is a fork that is no longer > maintained. Look at rope git [1] vs rope_py3k hg [2]. > > [1]:https://github.com/python-rope/rope/commits/master > [2]:https://bitbucket.org/agr/rope_py3k/commits/all I hadn't realised rope_py3k is a fork that is no longer maintained. I just saw it cited in the source of spyder-2.3.0. No longer maintained renders it unsuitable for using as a dep to a py3 capable bump of spyder which at face value means spyder is not in any fit state to support py3 in gentoo due to the dep on rope. Is there any path to oppose this conclusion?
So I've looked into it a bit more and it's harder than that. Since rope gets pretty deep down Python internals, it's not easy for it to support both Python 2 & 3. Then, rope is pretty much unmaintained. The new releases of rope are pretty much done by non-maintainer who just merges pull requests and other patches. He's willing to add Python 3 support but needs someone to do it :). About rope_py3k, it's hard even to call it a fork. It's pretty much a rewrite done to do a similar thing in Python 3. It's (un-)maintained by a different person, has different codebase (so not easy to merge it back) and doesn't really see much interest.
It was always possible, see ebuild. Sorry for the delay. *spyder-2.3.1 (15 Oct 2014) 15 Oct 2014; Ian Delaney <idella4@gentoo.org> +files/spyder-2.3.1-build.patch, +spyder-2.3.1.ebuild, -files/spyder-2.1.11-disable_sphinx_dependency.patch, -files/spyder-2.1.13-disable_sphinx_dependency.patch, -files/spyder-2.1.13-qt_requirements.patch, -files/spyder-2.2.1-disable_sphinx_dependency.patch, -spyder-2.1.11.ebuild, -spyder-2.1.13-r1.ebuild: bump; patch by Arfever to correct obligatory doc builds and incorrect install of data files, add py3 support, update deps, fixes Bug 517228, rm old
