- If this package could support installation for multiple versions of Python, then please try to adjust the ebuilds to support it. - Ensure that the ebuilds do not use deprecated functions or variables. - Please check if Python 3 is supported by this package. - If this package does not support Python 3: - Specify dependency on Python 2. You can use PYTHON_DEPEND helper variable, which should be set before inheriting of python eclass. - If this package cannot support installation for multiple versions of Python, then set active version of Python using python_set_active_version(). - Ensure that shebangs in installed scripts specify correct version of Python. If shebangs are too generic (e.g. '#!/usr/bin/python'), then you can use python_convert_shebangs() to convert shebangs. (Wrapper scripts generated by python_generate_wrapper_scripts() do not require any changes.) Please see documentation [1] for more details. [1] http://www.gentoo.org/proj/en/Python/developersguide.xml
Created attachment 223197 [details, diff] orca-2.28.3.ebuild.patch I'm attaching not tested patch, which probably works correctly.
Dependencies of app-accessibility/orca need to be fixed first.
Created attachment 250281 [details] orca.ebuild.diff Hello Arfrever I am trying to fix these python bugs while bumping Gnome 2.32 but I have seen I am unable to make orca work on a system with python3.1 as main python interpreter. Even running "python_convert_shebangs -r 2 ." in src_prepare doesn't fix the problem (like it does with accerciser), and I still get the following error at runtime: $ orca Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/orca/orca.py", line 1950 print msg ^ SyntaxError: invalid syntax If you know how to handle this, please tell me what to do. Thanks a lot :-)
Maybe "orca" script is generated later, so check if calling python_convert_shebangs() in src_install() helps. If it doesn't help, then please attach "orca" script.
Created attachment 250871 [details] orca.py orca.py is already present on "fresh" upstream sources, I attach it
I meant "orca", not "orca.py".
(In reply to comment #4) > Maybe "orca" script is generated later, so check if calling > python_convert_shebangs() in src_install() helps. If it doesn't help, then > please attach "orca" script. > That neither works :-(
Created attachment 251039 [details] /usr/bin/orca
(In reply to comment #8) runOrca() function needs to be fixed. sed -e "s:/usr/bin/python:$(PYTHON -a):" ...
(In reply to comment #9) > (In reply to comment #8) > > runOrca() function needs to be fixed. > sed -e "s:/usr/bin/python:$(PYTHON -a):" ... > It's is being generated from orca.in that has the following: runOrca() { exec_prefix=@prefix@ PYTHONPATH=${PYTHONPATH}:@pyexecdir@ export PYTHONPATH saveXmodmap @PYTHON@ -c "import orca.orca; orca.orca.main()" "$ARGS" restoreXmodmap } Maybe it should look different to properly detect python version? :-/
Fixed in 2.32, thanks a lot Arfrever