upstream 945744 https://github.com/wesnoth/wesnoth/issues/1508
thanks
On Wed, Nov 27, 2019 at 11:58:54PM +0000, Sandro Tosi wrote:
> Source: wesnoth-1.14
>
> binary:wesnoth-1.14-tools Depends->python
Hi,
I'd suggest just making the wesnoth-1.14-tools package depend on python3, as
the package already has a mixture of python2 and python3 scripts. The upstream
bug is going to be fixed for wesnoth-1.16, below is what happened to the
scripts.
In 1.14.9 a Python3 version is already side-by-side with the Python2 version:
data/tools/wesnoth/wmliterator.py
data/tools/wesnoth/wmlparser2.py
data/tools/wesnoth/wmltools.py
Obsolete and simply deleted in the 1.16 branch:
data/tools/journeylifter
data/tools/scoutDefault.py
data/tools/wesnoth/wmlgrammar.py
utils/wescamp_import
Depends on Gimp, left as python2 until Gimp 3 comes out:
data/tools/rmtrans/rmtrans.py
Ported to python3 in the 1.16 branch:
data/tools/expand-terrain-macros.py
data/tools/wesnoth/wmldata.py
data/tools/wmlflip
data/tools/wesnoth/wmlparser.py
utils/ai_test/ai_test.py
utils/codelist
utils/umc_dev/build/update_version
utils/unused_functions.py
utils/wiki_grabber.py
Replaced with a new tool in 1.16:
data/tools/trackplacer (python2 version also depends on pygtk)
data/tools/wmlvalidator
Not an official statement from upstream, just my understanding of the IRC chat:
The release date of 1.16 has been postponed until it's ready, definitely not in
the near future. The new target for 1.16 is whenever the player-visible content
is much better than 1.14, and we may keep raising that bar by backporting
content to 1.14 as long as it doesn't break multiplayer network compatibility.
BR,
Steve