Mark ninja-ide-2.3.ebuild stable.
amd64 stable
This version builds correctly, but python3 support is apparently broken upstream for the moment. If the python3.* interpreter is selected as default, attempting to start ninja-ide-2.3 provides in the following error: >>>>>>>>>>>>>>>>>>>>>>>>>> Traceback (most recent call last): File "/usr/bin/ninja-ide-python3.2", line 9, in <module> load_entry_point('NINJA-IDE==2.3', 'gui_scripts', 'ninja-ide')() File "/usr/lib64/python3.2/site-packages/ninja_ide/__init__.py", line 64, in setup_and_run from ninja_ide import core File "/usr/lib64/python3.2/site-packages/ninja_ide/core/__init__.py", line 23, in <module> from ninja_ide.core import settings File "/usr/lib64/python3.2/site-packages/ninja_ide/core/settings.py", line 25, in <module> from ninja_ide import resources File "/usr/lib64/python3.2/site-packages/ninja_ide/resources.py", line 35, in <module> PRJ_PATH = os.path.abspath(os.path.dirname(__file__)).decode('utf-8') AttributeError: 'str' object has no attribute 'decode' >>>>>>>>>>>>>>>>>>>>>>>>>>
seems I messed up was that problem already in 2.2? I remember using it with python3. anyway, dropped all python3* from PYTHON_COMPAT for now + 22 Aug 2013; Julian Ospald <hasufell@gentoo.org> ninja-ide-2.3.ebuild: + drop broken python versions wrt #480790
and upstream advertises python3 compatibility :(
Yes, upstream does advertise python3 compatibility! One of the devs said it would be fixed by the next release. I'm not really sure how 2.3 got out the door with that bit of borkery. Version 2.2 did not have this problem. Thanks!
(In reply to Aaron Burnett from comment #5) > Yes, upstream does advertise python3 compatibility! One of the devs said it > would be fixed by the next release. I'm not really sure how 2.3 got out the > door with that bit of borkery. Version 2.2 did not have this problem. > > Thanks! Well, autocompletion is broken in 2.2 as well, so I removed python3 from all of them.
x86 stable. Last arch, closing