Python Exceptions in Fly logs are cut off

Hello!
We’re trying to work with fly for a Python app, but our stack traces are cutoff which is kinda annoying. We’re currently working around this by catching an error and writing a json with traceback, but this doesn’t seem ideal.

The docs describe a method for Laravel for full stack traces (Deploy a Laravel Application · Fly Docs) - is there anything similar for Python? Or in general, is there anything else you’d recommend so that the Fly web log-viewer UI has better error logs?

1 Like