Python Language Summit 2026 - #137
Open
sethmlarson wants to merge 2 commits into
Open
sethmlarson wants to merge 2 commits into
sethmlarson wants to merge 2 commits into
Conversation
sethmlarson
requested review from
ambv,
emilyemorehouse,
hugovk and
lysnikolaou
September 26, 2026 21:47
Member
Should be fine :) If you did want to wrap, Prettier (like Black for JS) could do it, something like this: bunx prettier@3 --prose-wrap=always --print-width=88 \
--embedded-language-formatting=off \
--write "content/posts/language-summit-2026*/index.md" |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Landing page, 10 full-length blog posts, and 5 short "lightning" talk summaries detailing the Python Language Summit 2026.
Apologies in advance if leaving review comments is a little wonky, many (but not all) of the paragraphs are on single lines instead of having line breaks. That is an artifact of using Google Docs for a majority of the work and then using their "Docs to Markdown" tool to export the documents once we decided we'd be publishing to the Python Insider Blog.
TODOs: