Raise log level to help debug

How to Debug Python Trading Code

Follow this guide to effectively raise log level settings when debugging Python trading code. Using proper log levels helps diagnose problems quickly in your algorithmic trading strategies.

Raise log level for debugging Python trading

Debugging a code is frustrating. We understand it and we are here to help you. When you post debugging questions at community and send email to IBridgePy@gmail.com, please follow this guideline so that we can help you solve the issues quickly.

EXCLUSIVE OFFER

Extra 7% OFF All Quantra Courses

Level up your quant trading skills with courses from Quantra by QuantInsti — Python for trading, machine learning strategies, options trading, and more.

HUI7 Browse Courses → Use code HUI7 at checkout

1. Add this to RUN_ME.py, refer to this API doc. The last few lines are critical for us to understand what happened and what caused errors.

logLevel = ‘DEBUG’

The log file is stored at IBridgePy folder/Log and the file name is TraderLog_year-month-day.txt

Need help building this strategy?

Our Rent-a-Coder team builds custom automated trading programs. From simple scripts to complex multi-account strategies — we handle it all.

Sometime, you may even raise the logLevel to “NOTSET”, which will display all IBridgePy steps in the log.

2. Please tell more details about how to reproduce the bug.

3. Read this webpage and provide enough infor. https://ibridgepy.com//rent_a_coder/#Free_debug_service

Learn more from Python official documentation.

EXCLUSIVE OFFER

Extra 7% OFF All Quantra Courses

Level up your quant trading skills with courses from Quantra by QuantInsti — Python for trading, machine learning strategies, options trading, and more.

HUI7 Browse Courses → Use code HUI7 at checkout

Ready to Automate Your Trading?

Download IBridgePy free or let our coders build your strategy.

Download Free Hire a Coder

Leave a Comment