2024-07-14 14:49:44 -07:00
|
|
|
Done:
|
|
|
|
x Handle bundling of the actual Python modules we want to use.
|
2024-07-14 12:58:20 -07:00
|
|
|
x Remove dependency on psutil.
|
2024-07-14 14:49:44 -07:00
|
|
|
x Clean up removal of psutil.
|
|
|
|
x remove parent_pid from wrapper script
|
|
|
|
x remove KiriPythonRPCWrapper_start.py
|
|
|
|
x remove test_rpc.py
|
2024-07-14 18:40:49 -07:00
|
|
|
x Un-thread the GDScript side of PacketSocket.
|
|
|
|
x Fix whatever this is: <stuff was here>
|
|
|
|
x example Python module from OUTSIDE the addon
|
|
|
|
x Remove xterm dependency, or make it like a debug-only thing.
|
2024-07-15 07:39:58 -07:00
|
|
|
x Test on WINE/Windows.
|
|
|
|
x First-time setup of requirements (pip, etc).
|
2024-07-21 19:25:19 -07:00
|
|
|
x Deal with interrupted setup operations
|
|
|
|
x We check for the python.exe file in a given setup location to see if
|
|
|
|
we need to unpack stuff, but what if that exists but the setup was
|
|
|
|
interrupted and we're missing files?
|
|
|
|
x Deal with bad state after interrupted unpacking operation
|
2024-07-14 14:49:44 -07:00
|
|
|
|
|
|
|
The big ones:
|
2024-07-14 12:58:20 -07:00
|
|
|
|
2024-07-21 19:25:19 -07:00
|
|
|
- Add some kind of progress bar, or API for progress tracking, for the unpacking.
|
|
|
|
- Progress bar or API for progress tracking for pip installs.
|
|
|
|
- Maybe we should parse the pip requirements.txt and also set up an API for calling pip install.
|
2024-07-14 14:49:44 -07:00
|
|
|
- Documentation.
|
|
|
|
- how to use .kiri_export_python
|