Migrating Pology to Python 3

Karl Ove Hufthammer karl at huftis.org
Wed Oct 5 18:20:41 BST 2022


Adrian Chaves skreiv 04.10.2022 23:37:
>
> When running a script, either the repository clone folder should be 
> the current working folder, or pology should be installed in the 
> current Python virtual environment. The exception suggests to me that 
> neither is the case. There have been import behavior changes in Python 
> 3 that might explain that it worked before, but I do not think this is 
> something we should fix in pology itself.
>
I have tried running either scripts/posummit.py or bin/posummit from 
either pology/, pology/scripts or pology/bin (stripping the folder 
prefix when I’m inside the folder). But in all cases I get an error 
message like this one:

Traceback (most recent call last):
  File "/path/to/pology/bin/./posummit", line 21, in <module>
    from pology import version, _, n_, t_, PologyError
ModuleNotFoundError: No module named 'pology'

 From which folder should I run the script?

I have also tried building the project using cmake, but I get this error 
message:

CMake Error at pology/CMakeLists.txt:49 (install_python3_module_files):
  Unknown CMake command "install_python3_module_files".


-- 
Karl Ove Hufthammer



More information about the kde-i18n-doc mailing list