xraypy / _xraylarch_attic Goto Github PK

errors in plugin codes are not well described.

This causes a bug (for instance if a function def is in a function, it will not have "popped" arguments the second time through).
Similar to error recently fixed in on_boolop().

most are broken due to changes merged with join_asteval, unittest from asteval should be copied, modified

having 'larch' passed into plugins makes for conflicts with a straight 'import larch'...

FeffPath -- scattering from 1 path
FeffCalc -- the settings for 1 feff run

These could be just plain Groups, but perhaps having a special derived Group (so that integrity checks can be done by checking the class type) is worthwhile

Right now, a complete read-eval-print loop is a bit cumbersome to construct. Also, most of the plugins get passed a reference to the running interpreter, but not the inputText portion. And, they mostly use the symboltable and raise_exception parts of the Interpreter.....