Python Scripting Feedback Thread

[Jamie_Dale]

@rokel_race

Some functions prone to crashing the editor, mostly due to issues around deleting actors or assets.

Let us know if you find specifics. Our goal is the editor should never crash via Python.

@rokel_race

Python 2. Why?

I’ve answered this question elsewhere: https://forums.unrealengine.com/unre…why-python-2-7

@rokel_race

No web documentation on the API. This would be very easy to autogenerate.

We have Sphinx generation working for 4.20. I’m not 100% sure if it will be hosted online yet, but you’ll definitely be able to generate it locally.

@rokel_race

Pythonic indexing doesn’t work with ArrayProperties (e.g. x-1] for last element).

My bad. I’ll put in a bug for that. Edit: Fixed for 4.20.

@rokel_race

Using command line interface for running scripts is not optimal; they should be a proper asset which can be run from the context menu or something.
Being able to create custom slate windows / buttons for entering arguments and running would be ideal.

Yeah, we have plans to add support for menu extensions and UI creation in Python (likely via UMG), however this won’t be coming in 4.20.

@rokel_race

Long running scripts (e.g. importing hundreds of assemblies) give no progress of indication.

4.20 adds unreal.ScopedSlowTask to let you report long-running progress like this.

@rokel_race

No development environment -> no autocompletion.

4.20 generates a stub unreal.py file (when developer mode is enabled in the plugin settings) that can be used with external IDEs for auto-complete (we also use it for Sphinx generation).