Please give full error context on errors

[apalazzi]

When I try to use openseespy in my own environment I sometimes get errors like the following:

Traceback (most recent call last):
  File "my_file.py", line 350, in <module>
    ops.element('elasticBeamColumn',
    ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
                el_tag_counter, n1, n2,
                ^^^^^^^^^^^^^^^^^^^^^^^
    ...<6 lines>...
                transfTag,
                ^^^^^^^^^^
    )
    ^
opensees.OpenSeesError: See stderr output

which doesn't help at all in finding what's the issue... the full error should instead be printed to stderr to give people as much context as possible.

[mhscott]

The interpreter is telling you the line number, which helps. You can also print the exception:

https://portwooddigital.com/2023/09/10/gotta-catch-em-all/

[apalazzi]

@mhscott yes, but the line itself doesn't say much about what is wrong in the function call, and - maybe it wansn't clear in my message - in my output I don't have any useful output on stderr to understand the issue, that's the problem.
With the line number being the only hint about the issue I can only try and guess what's wrong, which is rather time consuming and frustrating: a more extensive output would really help in catching bugs in my scripts.