Grokcore.startup

Latest version: v4.1

Safety actively analyzes 723650 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

1.2

================

- Added new IPython-based interactive debugger which is used
automatically when IPython is available. Otherwise the gdb-style
debugger is provided.

1.1

================

- Drop zdaemon support.

- Close the database explicitely when execing a script through the
``interactive_debug_prompt``. This came to light in tests on Windows, as the
tests would try to delete the temp directory it created with the still
unclosed database file in there.

1.0.2

==================

- Somehow the intended fix in 1.0.1 did not actually get included in that
release. We make the fix again.

1.0.1

==================

- When passing a script to the interactive_debug_prompt command, one would
expect to be able to do: `if __name__ == '__main__':`, however __name__ would
be "__builtin__". This is fixed.

1.0

================

- Amend the interactive_debug_prompt function to behave more or less like the
"old" zopectl command. Whenever there's commandline arguments passed to the
command, the first one is assumed to be a python script that is 'execfile'd.
This allows ad hoc scripts to run against the setup application.

- Make package comply to zope.org repository policy.

- The upgrade notes will be moved to the Grok upgrade notes.

- Define entry points for main and debug application factories in
grokcore.startup.

- Use the groktoolkit.

0.4

================

- Fix documentation bugs.

Page 2 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.