My experience with this plugin so far is that once this issue occurs the limited code completion that is available completely stops working. Also, the syntax highlighting becomes quite inconsistent and wonky.

Greetings. Please note Python support is currently a work in progress and we are working to bring it to both feature completion and stability.

Can you please provide concrete steps to reproduce, so we can fix this issue?

Thanks.

This code reproduces the issue with the same general outcome.

#! /usr/bin/env python

def test_func(p1, p2, p3):
    return p1 * p2 * p3

if __name__ == '__main__':
    try:
        val = test_func(1, 2, 3)
    except Exception as e:
        print 'oops'

(In reply to whistler11783 from comment #3)
> This code reproduces the issue with the same general outcome.
> 
> #! /usr/bin/env python
> 
> def test_func(p1, p2, p3):
>     return p1 * p2 * p3
> 
> if __name__ == '__main__':
>     try:
>         val = test_func(1, 2, 3)
>     except Exception as e:
>         print 'oops'

In addition, this code causes the object navigator to become unpopulated due to the thrown exception.

(In reply to whistler11783 from comment #4)
> (In reply to whistler11783 from comment #3)
> > This code reproduces the issue with the same general outcome.
> > 
> > #! /usr/bin/env python
> > 
> > def test_func(p1, p2, p3):
> >     return p1 * p2 * p3
> > 
> > if __name__ == '__main__':
> >     try:
> >         val = test_func(1, 2, 3)
> >     except Exception as e:
> >         print 'oops'
> 
> In addition, this code causes the object navigator to become unpopulated due
> to the thrown exception.

This code causes this stack trace:
Annotation: Was parsing /workareas/main/work_server.py
Annotation: Was parsing /workareas/main/work_server.py
Was parsing /workareas/main/work_server.py
Was parsing /workareas/main/work_server.py
Caused: java.lang.ClassCastException: org.python.antlr.PythonErrorNode cannot be cast to org.python.antlr.base.excepthandler
	at org.python.antlr.ast.TryExcept.<init>(TryExcept.java:127)
	at org.python.antlr.GrammarActions.makeTryExcept(GrammarActions.java:224)
	at org.python.antlr.PythonParser.try_stmt(PythonParser.java:7257)
	at org.python.antlr.PythonParser.compound_stmt(PythonParser.java:6325)
	at org.python.antlr.PythonParser.stmt(PythonParser.java:2401)
	at org.python.antlr.PythonParser.suite(PythonParser.java:7761)
	at org.python.antlr.PythonParser.if_stmt(PythonParser.java:6443)
	at org.python.antlr.PythonParser.compound_stmt(PythonParser.java:6283)
	at org.python.antlr.PythonParser.stmt(PythonParser.java:2401)
	at org.python.antlr.PythonParser.file_input(PythonParser.java:630)
[catch] at org.netbeans.modules.python.editor.PythonParser.parse(PythonParser.java:303)
	at org.netbeans.modules.python.editor.PythonParser.parse(PythonParser.java:142)
	at org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:610)
	at org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:245)
	at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:733)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)

*** Bug 184218 has been marked as a duplicate of this bug. ***

Likely fixed as a result of the GSF-to-CSL conversion, 
I am unable to replicate the error using your test case and NetBeans IDE Dev 201505170001, on a Windows 8.1 box. Therefore marking as Fixed.

Reporter: Please try with the latest development build of Netbeans and let us know what you find! Reopen if necessary...

This parsing error affect:

#pass example

try:
  pass
except Exception:
  pass

#fail example

try:
  pass
except Exception as e:
  pass

Reporter: Please copy the information from Help->About and paste it here like you did in your initial report. Note: We are not making any fixes to 8.0.2; only 8.1 is supported at this time.
Thank you.

Hi,

I cannot reproduce with 8.1. Marking the bug as fixed. If you still experience this bug with 8.1, please reopen.