Global: Python Options

DBT includes an integrated interpreter for running Python scripts, which can be used for importing PDF files and for editing macros. This dialog controls certain technical aspects of the Python interpreter. The settings are sure to be of interest to Python developers wishing to enhance DBT and may also be needed to solve some problems when you contact Duxbury technical support.

Chances are that you will never need to use this dialog unless you are developing macros for DBT.

Custom Library Path: This is normally left blank. DBT has all of the Python library files it requires to run the scripts that come with DBT. However, if your own scripts require library files that are not shipped with DBT (but are Python 3 compatible) you can enter one or more directories into this field. Separate multiple directories with a semicolon. For example, to connect DBT to Python as you use it on the command line, you might invoke "python3" then give the following two commands at the interactive prompt:

import sys
print(';'.join(sys.path[1:]))

The output of that command can be copied and pasted into the Custom Library Path, giving DBT access to all the libraries installed for your command line use.

Include Built-in Library allows DBT to use the library files bundled with DBT. It is generally a good idea to leave this checked unless some library bundles with DBT is causing a problem for you. Clearing this setting may cause problems for PDF imports.

Logging Level: is set to any of the allowable levels supported by the standard Python logging facility. All log messages of that level or above, which are generated when running Python code, will be logged to the destination entered as the Logging Destination. Thus, selecting Debug logging causes all log messages to appear, while selecting Critical logging results in relatively few messages. Critical and Error messages are always displayed on screen, if any are generated, immediately after Python code has been run. The setting in this dialog controls only the logging level for an external file you may set up.

Logging Destination: is the full path and name of a file to which Python log messages should be written. Because DBT is not a console application, this can be very helpful when debugging Python scripts. DBT will create the file if it does not exist, and will append to it if it does exist. The file must be writable. You will want to periodically clear out the file or disable logging, because logging can use quite a lot of space over time, particularly with Debug or Info level logging. If this field is left blank, messages are logged to a dialog displayed by DBT. The dialog is used, in any case, to log Critical and Error messages logged from Python.