Skip to content

MAINT Breaking: Remove MemoryExporter and export_conversations#1856

Open
rlundeen2 wants to merge 3 commits into
microsoft:mainfrom
rlundeen2:rlundeen2/remove-memory-exporter
Open

MAINT Breaking: Remove MemoryExporter and export_conversations#1856
rlundeen2 wants to merge 3 commits into
microsoft:mainfrom
rlundeen2:rlundeen2/remove-memory-exporter

Conversation

@rlundeen2
Copy link
Copy Markdown
Contributor

Deletes the MemoryExporter strategy class and its public consumers:

  • pyrit/memory/memory_exporter.py
  • MemoryInterface.export_conversations / self.exporter
  • SQLiteMemory.export_conversations override and export_all_tables
  • _ExportableConversationPiece helper
  • Associated unit tests and doc/code/memory/9_exporting_data notebook

Users who need export can use the output module or serialize directly

rlundeen2 and others added 2 commits May 29, 2026 16:53
Deletes the MemoryExporter strategy class and its public consumers:
- pyrit/memory/memory_exporter.py
- MemoryInterface.export_conversations / self.exporter
- SQLiteMemory.export_conversations override and export_all_tables
- _ExportableConversationPiece helper
- Associated unit tests and doc/code/memory/9_exporting_data notebook

Users who need export can call get_message_pieces and serialize with
pandas / json.dump directly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

return seed_groups

def export_conversations(
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought this made the most sense just to delete vs deprecate. But open to push back

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should deprecate. There's no harm in waiting for one release at least. I don't mind shortening it to just one release for this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, especially since we have a release coming up.

Maybe merge this pre-release: #1870
then we can merge this one post release

…ry-exporter

# Conflicts:
#	pyrit/memory/memory_exporter.py
#	pyrit/memory/memory_interface.py
#	pyrit/memory/sqlite_memory.py
#	tests/unit/memory/memory_interface/test_interface_export.py
#	tests/unit/memory/test_memory_exporter.py
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