When manually debugging data functions, I will often separate the DF into two files: one containing the DF itself (so that it can be copied to or from Spotfire), and one that loads the script from the first file and uses the classes in spotfire.data_function to manage the rest of the flow.
However, it is not possible to set breakpoints in that first script and have them trigger under a debugger, since the data function flow classes set a fake filename of "<data_function>" (so that backtraces reported back to Spotfire do not confuse the user with temporary filenames).
Add a method to the spotfire.data_function classes to allow setting a real filename.
When manually debugging data functions, I will often separate the DF into two files: one containing the DF itself (so that it can be copied to or from Spotfire), and one that loads the script from the first file and uses the classes in
spotfire.data_functionto manage the rest of the flow.However, it is not possible to set breakpoints in that first script and have them trigger under a debugger, since the data function flow classes set a fake filename of "
<data_function>" (so that backtraces reported back to Spotfire do not confuse the user with temporary filenames).Add a method to the
spotfire.data_functionclasses to allow setting a real filename.