<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>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.</p>
<p id="reply-intro">On 2022-10-04 19:26, Johnny Jazeix wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div>
<div dir="ltr">
<div>Hi,</div>
<div> </div>
<div>for French we use the script in <a href="https://websvn.kde.org/trunk/l10n-support/fr/summit/scripts/sync_summit_branches.sh?view=log" target="_blank" rel="noopener noreferrer">https://websvn.kde.org/trunk/l10n-support/fr/summit/scripts/sync_summit_branches.sh?view=log</a> to do the merge/scatter jobs.</div>
<div>It clones the pology and ll10n-scripty git repos and the svn for the required locale and do the merge/scatter.</div>
<div> </div>
<div>Locally, I commented the "svn ci" just in case... I tested the branch python3 and I have the following error:</div>
<div>Merging messages<br />Traceback (most recent call last):<br /> File "/home/jazeix/Desktop/travail/kde_i18n_fr//pology/scripts/posummit.py", line 21, in <module><br /> from pology import version, _, n_, t_, PologyError<br />ModuleNotFoundError: No module named 'pology'</div>
<div> </div>
<div>I haven't digged more but it happens when we do the line: "posummit.pyscripts/messages.summit fr merge".</div>
<div>Cheers,</div>
<div> </div>
<div>Johnny</div>
<div> </div>
</div>
<br />
<div class="v1gmail_quote">
<div class="v1gmail_attr" dir="ltr">Le mar. 4 oct. 2022 à 12:49, Adrian Chaves <<a href="mailto:adrian@chaves.io" rel="noreferrer">adrian@chaves.io</a>> a écrit :</div>
<blockquote class="v1gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;">
<div style="font-size: 10pt; font-family: Verdana,Geneva,sans-serif;">
<p>Hey!</p>
<p>In the i18n BoF at Akademy we are discussing quickly migrating Pology to Python 3, since Python 2 is end of life.</p>
<p>In 2020, I spent 1 day migrating Pology to Python 3. I created a single test that covered 7% of its code base, got it working under Python 3, and pushed the changes to the python3 branch: <a href="https://invent.kde.org/sdk/pology/-/tree/python3" target="_blank" rel="noopener noreferrer">https://invent.kde.org/sdk/pology/-/tree/python3</a></p>
<p>I have just merged the master branch into this branch, and the test still passes.</p>
<p>So I would like every Pology user to test as soon as possible their usual workflows with pology with the python3 branch, and report to me any issue. I do expect there to be issues. So send me a command to reproduce the issue you get, and I will fix it.</p>
<p>The plan is to switch the master branch from Python 2 to Python 3 rather soon, as I do not expect to have spare time for Pology once Akademy is over. So please, test the python3 branch as soon as possible, and send your feedback.</p>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<p><br /></p>
</body></html>