Skip to content

Best-of update: 2026.04.02#45

Open
github-actions[bot] wants to merge 1 commit intomainfrom
update/2026.04.02
Open

Best-of update: 2026.04.02#45
github-actions[bot] wants to merge 1 commit intomainfrom
update/2026.04.02

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 2, 2026

To finish this update: Select Merge pull request below and Confirm merge. Also, make sure to publish the created draft release in the releases section as well.

High-level PR Summary

This is an automated best-of list update for the date 2026.04.02 that refreshes project metrics, rankings, and trend indicators. The update tracks changes in project quality scores, showing domonic and yattag trending up while wtforms, lxml, domify, tagz, and rusty-tags are trending down. The changes include updated star counts, rankings, contributor numbers, and other project metadata across HTML generation and form generation libraries.

⏱️ Estimated Review Time: 5-15 minutes

💡 Review Order Suggestion
Order File Path
1 latest-changes.md
2 history/2026-04-02_changes.md
3 history/2026-04-02_projects.csv
4 README.md

Need help? Join our Discord

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Apr 2, 2026

Reviewer's Guide

Updates the HTML generation projects catalog and trending metadata for the 2026‑04‑02 best-of refresh, including promoting domonic and yattag, adjusting scores/stats for several projects, moving some entries between main and hidden lists, and recording the snapshot in the history directory.

State diagram for project visibility and trending status in catalog

stateDiagram-v2
    [*] --> Evaluated

    state Evaluated {
        [*] --> Hidden
        Hidden --> Visible: Meets_visibility_threshold
        Visible --> Hidden: Falls_below_threshold
    }

    Evaluated --> TrendingUp: Score_increased_since_last_snapshot
    Evaluated --> TrendingDown: Score_decreased_since_last_snapshot
    Evaluated --> Neutral: Score_unchanged

    TrendingUp --> Evaluated: Next_best_of_refresh
    TrendingDown --> Evaluated: Next_best_of_refresh
    Neutral --> Evaluated: Next_best_of_refresh
Loading

Flow diagram for best-of catalog refresh and history snapshot

flowchart TD
    SourceData[(Project_metrics_sources)] --> UpdaterScript
    UpdaterScript[[Best_of_updater_2026_04_02]] --> ComputeScores[Compute_project_quality_scores]
    ComputeScores --> ClassifyVisibility{Meets_min_requirements}

    ClassifyVisibility -- yes --> VisibleList[README_HTML_projects_section]
    ClassifyVisibility -- no --> HiddenList[README_hidden_projects_block]

    ComputeScores --> DetectTrending[Detect_trending_up_down]

    DetectTrending --> LatestChanges[latest_changes_md]
    DetectTrending --> HistoryChanges[history_2026_04_02_changes_md]
    DetectTrending --> HistoryCsv[history_2026_04_02_projects_csv]

    VisibleList --> Commit[Git_commit]
    HiddenList --> Commit
    LatestChanges --> Commit
    HistoryChanges --> Commit
    HistoryCsv --> Commit

    Commit --> PR[Best_of_update_2026_04_02_PR]
    PR --> Merge[Merge_pull_request]
    Merge --> Release[Draft_release_for_2026_04_02]
Loading

File-Level Changes

Change Details Files
Refresh HTML generation project entries in README to reflect latest scores, statuses, and visibility for the 2026-04-02 snapshot.
  • Replace lxml as the leading example project with domonic in the HTML generation section and insert a note about hidden projects below it.
  • Reinsert lxml as a separate details block with updated project-quality score and last-activity date.
  • Update stats for htpy and ludic (stars, issue counts, open percentages, and timestamps).
  • Move enaml-web from a visible top-level entry into the hidden projects list and adjust its score and status.
  • Reorder and adjust several hidden projects’ entries (yattag, htbuilder, MarkupPy, INUI, domify, fast_html, python-hiccup, hyperpython, pyhead, tagz, rusty-tags) including updated scores, star counts, and status markers (💀/🛌/📉).
  • Mark wtforms as trending down in README and update its GitHub stats (download count) in the forms section.
README.md
Update latest-changes overview to align with the new trending up/down projects for this snapshot.
  • Replace lxml in the trending up list with domonic and yattag, reflecting their improved scores and statuses.
  • Replace the previous trending down entries (yattag and css-generator placeholder) with wtforms, lxml, domify, tagz, and rusty-tags, including updated scores and trending indicators.
latest-changes.md
Record the 2026-04-02 snapshot in the history directory for auditability and per-date changelog tracking.
  • Add a dated markdown file mirroring the latest-changes.md trending up/down content for 2026-04-02.
  • Create a matching CSV placeholder/file for the 2026-04-02 projects snapshot (contents not shown in diff).
history/2026-04-02_changes.md
history/2026-04-02_projects.csv

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@recurseml recurseml bot left a comment

Choose a reason for hiding this comment

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

Review by RecurseML

🔍 Review performed on ada5f73..a48b1cb

✨ No bugs found, your code is sparkling clean

✅ Files analyzed, no issues (4)

README.md
history/2026-04-02_changes.md
history/2026-04-02_projects.csv
latest-changes.md

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've found 1 issue, and left some high level feedback:

  • In the new domonic entry, the description ends with a double period (port..); consider normalizing this to a single period to match the style of other entries.
  • The line _1 projects are hidden because they don't fulfill the minimal requirements._ should probably use singular agreement (1 project is hidden) to avoid a minor grammar issue.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In the new domonic entry, the description ends with a double period (`port..`); consider normalizing this to a single period to match the style of other entries.
- The line `_1 projects are hidden because they don't fulfill the minimal requirements._` should probably use singular agreement (`1 project is hidden`) to avoid a minor grammar issue.

## Individual Comments

### Comment 1
<location path="README.md" line_range="79" />
<code_context>
+
+<br>
+
+ _1 projects are hidden because they don't fulfill the minimal requirements._
+
+---
</code_context>
<issue_to_address>
**issue (typo):** Correct grammar in the "1 projects are hidden" sentence.

Use the singular form: `1 project is hidden because it doesn't fulfill the minimal requirements.`

```suggestion
_1 project is hidden because it doesn't fulfill the minimal requirements._
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.


<br>

_1 projects are hidden because they don't fulfill the minimal requirements._
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

issue (typo): Correct grammar in the "1 projects are hidden" sentence.

Use the singular form: 1 project is hidden because it doesn't fulfill the minimal requirements.

Suggested change
_1 projects are hidden because they don't fulfill the minimal requirements._
_1 project is hidden because it doesn't fulfill the minimal requirements._

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.

1 participant