Skip to main content

discuss-nutshell

Actions Status Documentation Status PyPI version Conda-Forge PyPI platforms GitHub Discussion

Improve your understanding of long Discourse threads.

Problem statement

Discourse topics, such as on discuss.python.org, can get very long even over a few hours or days. These long threads makes it difficult to understand the conversation without spending one to three hours reading the thread. Discourse gives a predicted time to read the thread.

On discuss.python.org, discussion threads about an individual [Python Enhancement Proposal](https://peps.python.org], PEP, can get very long. To understand the pros and cons of the PEP, reading the thread is needed.

Motivation

I want a time-efficient way to read posts and summarize the key points. Ideally, I would like to understand the pros and cons of an individual PEPs. Understanding the authors' motivations and their background also is important.

Recapping the conversation in an accurate way would be very helpful.

Initial approach

Take a Discourse topic and parse it into posts that can be queried.

  • data_loader.py: Hit an endpoint and save to json
  • preprocessor.py: Do data cleaning and parsing into individual post files
  • launch_app.py: Launch gradio app to interact with the LLM and log queries, context, responses

Take the db file and use datasette to view: datasette data/posts_qa_logs.db

Summarize individual posts and aggregate the summarized posts into one posts file that can be queried.

Use a simple Gradio UI to interface with the user.

Next phases

Data to keep: Authors, date/time, post number, uuid post, core dev (bool), cooked message, summarized message

Possible prompts

  • Does this message support or refute the proposed PEP?
  • What are key topics found in the message
  • How many times has a person posted
  • You are a Python expert. Summarize this message.
  • You are an intermediate Python user. Summarize this message.
  • You are a manager not a developer. Summarize this message.

Report on pros and cons of the PEP proposal.

Query in 10 message chunks and summarize.

  • Create a visual display of individual posts, summaries, author, and date posted.
  • Display the summaries but allow the original post text to be accessed easily.
  • Plot a sentiment of messages over time.

Metadata

Release files for discuss-nutshell 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for discuss-nutshell 0.4.0
File Size Uploaded
discuss_nutshell-0.4.0.tar.gz 906.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for discuss-nutshell 0.4.0
File Interpreter ABI Platform
discuss_nutshell-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 922.0 kB

Release files / discuss_nutshell-0.4.0.tar.gz

Download URL discuss_nutshell-0.4.0.tar.gz
Size 906.8 kB
Tags Source
SHA-256 checksum
How to use checksums
8c40d8348e3257a595fc55e0648362ee898a044f2a5e97c115b42e275fec58ad
BLAKE2b-256 checksum
How to use checksums
9711d8b41da34099aa3af3f1aaf891eb8b3383edc1dfe3c420aab91166f9b53e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 27, 2025.

Transparency log

Release files / discuss_nutshell-0.4.0-py3-none-any.whl

Download URL discuss_nutshell-0.4.0-py3-none-any.whl
Size 15.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d5360de5d6ff6cc3a788c7607e300cdf75ae1b718aa1226a7dc8058192eb90d
BLAKE2b-256 checksum
How to use checksums
6bf2d26a5e0cbe216bf8756042e33881c867252d833626986343982295357854
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 27, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.0 This release

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page