Cannot run Python example with `java.security.ProtectionDomain` error.

[Spaxe]

Referring to https://github.com/jdf/processing.py/issues/208.

The error occurs on 3.1.1, but not version 3.0.1. I suspect there is something that Jython requires that is inaccessible in 3.1.1.

[GoToLoop]

This was also reported here, but for Java Mode: processing/processing-docs#436
Up till version 3.0.2 no java.security.ProtectionDomain was thrown.
But something very wrong happened to P3.1.1.
Here's the problematic code from the link above adapted to Python Mode:

'''
 ' selectInput() for loadImage() in settings() (v1.1)
 ' GoToLoop (2016-Jun-09)
 '
 ' Forum.Processing.org/two/discussion/16705/
 ' null-pointer-exception-when-loading-image-in-settings-p3-1-1#Item_1
 '
 ' https://GitHub.com/processing/processing/issues/4529
'''

RENDERER = JAVA2D # JAVA2D, FX2D, P2D, P3D, OPENGL
canvas = None

def settings():
    selectInput('Please select canvas picture:', 'selectImage')
    print 'Awaiting selecting image...\n' # needed for P3.1.1+
    while not canvas: delay(100)

    size(canvas.width, canvas.height, RENDERER)
    noSmooth()
    noLoop()

def draw(): background(canvas)

def selectImage(f):
    if not f or f.isDirectory():
        print "Window was closed or you've hit cancel."
        System.exit(0)

    canvasPath = f.getPath()
    print canvasPath

    global canvas
    canvas = loadImage(canvasPath)

    if not canvas:
        print 'is invalid image file. Try again...\n'
        selectInput('Please select canvas picture:', 'selectImage')

Works as intended under P3.0.2, but halts under P3.1.1 once it reaches loadImage().
Also there's this glitch selectInput() is stopped from happening @ P3.1.1 if delay() is followed right way!

[Spaxe]

Thanks @GoToLoop. I had thought it was a Python/Jython issue.

Hope someone can shine some lights.

[DominusDodo]

Revision 0251 seems to work fine, but not the current 3.1.1 (rev. 0250).

[Spaxe]

Thanks to @DominusDodo, this can be tracked with #4547

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.