johnsojc wrote:Deledrius wrote:johnsojc wrote:When I was looking for some little project to occupy my time, I considered trying to convert the scripts to Python3 but somewhere I read that PIL had not been updated to version 3 yet so I dropped that idea for now.
Plasma doesn't use PIL at all.
resources.dat?
Ah, well I can see why that is a bit confusing.
Plasma (the engine), and the Python scripts that it uses, do not use any third-party Python modules.
The script which builds our tiny portion of game data
does. Technically speaking, that script is part of the game data build process and not the engine, so it didn't occur to me at all when you mentioned it (because it's entirely irrelevant to what you're working on). The version of the Python executable used to build resource.dat has no necessary connection to the libraries used in the process of building the engine. I just happened to use a Python script as the tool to render the images we pack into the resource.dat, and it is
that automation script and that alone which relies currently on PIL. The ability to
turn off building the resource.dat was added recently by Mystler as a CMake option as well, since you don't need to build a new one very frequently at all (if ever).
Ideally that entire process should be moved to a separate repository, but as we don't have much game data being built currently it would be quite lonely.
That said, however, in addition to updating the scripts to be compliant with Python3, I suspect the engine will need to be tweaked for API changes in the Python library as well. Both the scripts you're working on and the engine itself will need work done to keep in step with each other. This is not a relatively high-priority task at this time, but if someone is interested in doing it the work is welcomed.