Gramex 1.88 release notes

Gramex 1.88 supports Breakpoint debugging and templates for the IDE.

Breakpoint Debugging

Gramex used to prefer ipdb as the default debugger. Now, Gramex uses the default breakpoint() mechanism.

In any FunctionHandler, transform, or any Python code, add breakpoint() to pause execution and enter the debugger.

You can replace the default Python debugger pdb by setting the PYTHONBREAKPOINT environment variable:

Run gramex init ide to create a new Gramex project that is used on the Gramex IDE.

This is a lightweight template that has:

The Gramex Docker build is now based on Alpine 3.17 (from 3.16). This is a security update. #676

The gramex command is now available from the PATH of the Gramex Docker images #683
CaptureHandler is refactored to use the more modern Puppeteer v19 (instead of v14) #686
Schedules now log the entire exception when a schedule fails, not just the error message #689
User store migrations from pre 1.87 gramex.auth.db to 1.87+ now work on Unix #678
Gramex will not use SQLAlchemy 2.x until full support across libraries becomes available #690

Gramex 1.88 is backward compatible with previous releases unless the release notes say otherwise. Automated builds test this.

Every Gramex release is tested for security vulnerabilities using the following tools.

The Gramex code base has:

22,184 lines of Python (18 more than 1.87)
3,626 lines of JavaScript (same as 1.87)
15,136 lines of test code (5 less than 1.87)
We are migrating to pytest from nose. Code coverage will be reported post migration.