Skip to content

DOC: Re-execute pyrit_initializer notebook to populate cell outputs#1718

Merged
romanlutz merged 1 commit into
microsoft:mainfrom
romanlutz:fix/pyrit-initializer-notebook-output
May 12, 2026
Merged

DOC: Re-execute pyrit_initializer notebook to populate cell outputs#1718
romanlutz merged 1 commit into
microsoft:mainfrom
romanlutz:fix/pyrit-initializer-notebook-output

Conversation

@romanlutz

Copy link
Copy Markdown
Contributor

What

doc/code/setup/pyrit_initializer.ipynb was committed with execution_count: null on every code cell. As a result, the published docs page at https://microsoft.github.io/PyRIT/code/setup/pyrit_initializer/ renders all 3 code cells with no output. Re-executing populates them:

  • Cell 2: the CustomInitializer instance repr
  • Cell 4: env-file loading + memory init via SimpleInitializer
  • Cell 6: temp-script creation and initialization via initialization_scripts

Notes

doc/code/setup/pyrit_initializer.ipynb was committed with execution_count: null on every code cell, so the published docs page (https://microsoft.github.io/PyRIT/code/setup/pyrit_initializer/) renders all 3 code cells with no output. Re-executing populates:

- Cell 2: the CustomInitializer instance repr
- Cell 4: env-file loading + memory init via SimpleInitializer
- Cell 6: temp script creation and initialization via initialization_scripts

Cell 2 contains a SyntaxWarning from upstream confusables 1.2.0 and the multiprocess SyntaxWarning addressed by microsoft#1709. The confusables one is unfixed upstream (we will audit our use of confusables in a follow-up). The multiprocess one will disappear from outputs once microsoft#1709 merges and notebooks are next re-executed.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@romanlutz
romanlutz added this pull request to the merge queue May 12, 2026
Merged via the queue into microsoft:main with commit c4b1876 May 12, 2026
47 checks passed
@romanlutz
romanlutz deleted the fix/pyrit-initializer-notebook-output branch May 12, 2026 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants