[BUG] - Lookup lists that are not valid Python variable names break the labeling function calculation

[DerEchteFeuerpfeil]

Describe the bug Lookup lists that are not valid variable names break the labeling function calculation even when they are not used. When I removed the list called "123" (see screenshot), the calculation worked again.

To Reproduce Steps to reproduce the behavior:

1. Create a lookup list called "123"
2. Import some list (dsnt have to be the 123 one) from knowledge in a LF
3. Run it
4. See error

Expected behavior Either I shouldnt be able to create such list names or the execution environment should preface the list name with something viable like "list_"

Screenshots

Desktop (please complete the following information):

• OS: win10
• Browser chrome
• Version 1.7.1

Additional context

[JWittmeyer]

possible solution could be to enhance the toPythonFunctionName function and match the logic to the backend version. Also important to note is that there is a second function currently in use which works slightly different and should be replaced asPythonVariable

• So no special characters (replace with '' - already included)
• case (whitespace changed to -> already included)
• lowercase (should be included but isn't part of the function atm)
• no starting numbers (prefixed with e.g. or list)