Slick-C Error inPython when typing "printf("

[JeppeOland]

Obviously because I'm not a Python guy except in a pinch, so "printf" is muscle memory.
Anyways ... type it in SlickEdit, and it helpfully replaces it with just "print", but also pops up an error:
"Variable element or variable not initialized. file=codehelp.ex offset=27306"
Sometimes the first part is just a ?.

[Dennis]

I will look into this.  Could you send the the most recent part of <slickedit-config-dir>/logs/stack.log ?

[Dennis]

Never mind, that was easier to reproduce than I expected.

[JeppeOland]

Similarly, typing "numpy.sign(" replaces with "sin()" and gives the same error.
(replacing in this case is wrong since there IS a sign function)

[Dennis]

You can turn off the auto-correct feature by going to Document > Python Options... > Completion Options > | | Auto-correct identifier before operator.  The same option applies both to "." operators and function argument help / open paren.

I might be able to tweak things to handle the "numpy" case, I assume that the reason that it tries to replace with "sin" is because it can not find numpy.sign.  You could try creating a language specific tag file for Python in order to have the numpy module tagged.

[JeppeOland]

Is "numpy" not being automatically tagged?

[Dennis]

Looks like our automatic Python tagging only gets the standard Python packages.  Numpy is an add-on.

It is a pretty commonly used package, I might look into adding information for it to our "python.tagdoc". 
It might be a good idea to add PyTorch too.  I will look into it.

[JeppeOland]

Yeah those are pretty common.
Stuff like matplotlib.pyplot is also pretty frequently used.

[Dennis]

The original problem will be fixed in the next beta.  The proportion of "easy to reproduce" / "easy to fix" for this one was out of this world.

[JeppeOland]

Best kind of bug there is (for the guy fixing it)