---
title: "Join us at PyCon US 2026 in Long Beach - we have new AI and security tracks this year"
source_name: "Simon Willison's Weblog"
original_url: "https://simonwillison.net/2026/Apr/17/pycon-us-2026/#atom-everything"
canonical_url: "https://www.traeai.com/articles/d800be1e-6893-4a29-a10d-f965f573ab24"
content_type: "article"
language: "英文"
score: 5.5
tags: ["Python","PyCon","AI","网络安全","开发者社区"]
published_at: "2026-04-17T23:59:03+00:00"
created_at: "2026-04-18T03:10:26.09927+00:00"
---

# Join us at PyCon US 2026 in Long Beach - we have new AI and security tracks this year

Canonical URL: https://www.traeai.com/articles/d800be1e-6893-4a29-a10d-f965f573ab24
Original source: https://simonwillison.net/2026/Apr/17/pycon-us-2026/#atom-everything

## Summary

PyCon US 2026将在长滩举办，新增AI与安全专题，强调社区参与和非正式交流。

## Key Takeaways

- PyCon US 2026首次在加州长滩举办，设有AI和安全两个新专题。
- AI专题涵盖本地大模型运行、浏览器端推理、异步模式等实用主题。
- 会议保留闪电演讲、开放空间和冲刺开发等强社区特色活动。

## Content

Title: Join us at PyCon US 2026 in Long Beach—we have new AI and security tracks this year

URL Source: http://simonwillison.net/2026/Apr/17/pycon-us-2026/

Published Time: Sat, 18 Apr 2026 02:38:53 GMT

Markdown Content:
# Join us at PyCon US 2026 in Long Beach—we have new AI and security tracks this year

# [Simon Willison’s Weblog](http://simonwillison.net/)

[Subscribe](http://simonwillison.net/about/#subscribe)

**Sponsored by:** Honeycomb — AI agents behave unpredictably. Get the context you need to debug what actually happened. [Read the blog](https://fandf.co/4sb46pb)

## Join us at PyCon US 2026 in Long Beach—we have new AI and security tracks this year

17th April 2026

This year’s [PyCon US](https://us.pycon.org/2026/) is coming up next month from May 13th to May 19th, with the core conference talks from Friday 15th to Sunday 17th and tutorial and sprint days either side. It’s in Long Beach, California this year, the first time PyCon US has come to the West Coast since Portland, Oregon in 2017 and the first time in California since Santa Clara in 2013.

If you’re based in California this is a great opportunity to catch up with the Python community, meet a whole lot of interesting people and learn a ton of interesting things.

In addition to regular PyCon programming we have two new dedicated tracks at the conference this year: an [AI track](https://us.pycon.org/2026/tracks/ai/) on Friday and a [Security track](https://us.pycon.org/2026/tracks/security/) on Saturday.

The AI program was put together by track chairs Silona Bonewald (CitableAI) and Zac Hatfield-Dodds (Anthropic). I’ll be an in-the-room chair this year, introducing speakers and helping everything run as smoothly as possible.

Here’s [the AI track schedule](https://us.pycon.org/2026/schedule/talks/#May15) in full:

*   11:00: [AI-Assisted Contributions and Maintainer Load](https://us.pycon.org/2026/schedule/presentation/105/)—Paolo Melchiorre
*   11:45: [AI-Powered Python Education : Towards Adaptive and Inclusive Learning](https://us.pycon.org/2026/schedule/presentation/66/)—Sonny Mupfuni
*   12:30: [Making African Languages Visible: A Python-Based Guide to Low-Resource Language ID](https://us.pycon.org/2026/schedule/presentation/23/)—Gift Ojeabulu
*   2:00: [Running Large Language Models on Laptops: Practical Quantization Techniques in Python](https://us.pycon.org/2026/schedule/presentation/138/)—Aayush Kumar JVS
*   2:45: [Distributing AI with Python in the Browser: Edge Inference and Flexibility Without Infrastructure](https://us.pycon.org/2026/schedule/presentation/126/)—Fabio Pliger
*   3:30: [Don’t Block the Loop: Python Async Patterns for AI Agents](https://us.pycon.org/2026/schedule/presentation/110/)—Aditya Mehra
*   4:30: [What Python Developers Need to Know About Hardware: A Practical Guide to GPU Memory, Kernel Scheduling, and Execution Models](https://us.pycon.org/2026/schedule/presentation/81/)—Santosh Appachu Devanira Poovaiah
*   5:15: [How to Build Your First Real-Time Voice Agent in Python (Without Losing Your Mind)](https://us.pycon.org/2026/schedule/presentation/101/)—Camila Hinojosa Añez, Elizabeth Fuentes

(And here’s [how I scraped that as a Markdown list](https://gisthost.github.io/?dab27f61d85eb98f60db5991aa21ec89) from the schedule page using Claude Code and [Rodney](https://github.com/simonw/rodney).)

#### You should come to PyCon US!

I’ve been going to PyCon for over twenty years now—I first went [back in 2005](https://simonwillison.net/2005/Mar/28/pycon/). It’s one of my all-time favourite conference series. Even as it’s grown to more than 2,000 attendees PyCon US has remained a heavily community-focused conference—it’s the least _corporate_ feeling large event I’ve ever attended.

The talks are always great, but it’s the add-ons around the talks that really make it work for me. The [lightning talks](https://us.pycon.org/2026/events/lightning-talks/) slots are some of the most heavily attended sessions. The PyLadies auction is always deeply entertaining. The sprints are an incredible opportunity to contribute directly to projects that you use, coached by their maintainers.

In addition to scheduled talks, the event has **open spaces**, where anyone can reserve space for a conversation about a topic—effectively PyCon’s version of an [unconference](https://en.wikipedia.org/wiki/Unconference). I plan to spend a lot of my time in the open spaces this year—I’m hoping to join or instigate sessions about both [Datasette](https://datasette.io/) and [agentic engineering](https://simonwillison.net/guides/agentic-engineering-patterns/).

I’m on the board of the Python Software Foundation, and PyCon US remains one of our most important responsibilities—in the past it’s been a key source of funding for the organization, but it’s also core to our mission to “promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers”.

If you do come to Long Beach, we’d really appreciate it if you could book accommodation in the official hotel block, for reasons [outlined in this post on the PSF blog](https://pyfound.blogspot.com/2026/04/pycon-us-2026-hotels.html).

Posted [17th April 2026](http://simonwillison.net/2026/Apr/17/) at 11:59 pm · Follow me on [Mastodon](https://fedi.simonwillison.net/@simon), [Bluesky](https://bsky.app/profile/simonwillison.net), [Twitter](https://twitter.com/simonw) or [subscribe to my newsletter](https://simonwillison.net/about/#subscribe)

## More recent articles

*   [Qwen3.6-35B-A3B on my laptop drew me a better pelican than Claude Opus 4.7](http://simonwillison.net/2026/Apr/16/qwen-beats-opus/) - 16th April 2026
*   [Meta's new model is Muse Spark, and meta.ai chat has some interesting tools](http://simonwillison.net/2026/Apr/8/muse-spark/) - 8th April 2026

This is **Join us at PyCon US 2026 in Long Beach—we have new AI and security tracks this year** by Simon Willison, posted on [17th April 2026](http://simonwillison.net/2026/Apr/17/).

[conferences 188](http://simonwillison.net/tags/conferences/)[open-source 302](http://simonwillison.net/tags/open-source/)[pycon 27](http://simonwillison.net/tags/pycon/)[python 1245](http://simonwillison.net/tags/python/)[ai 1964](http://simonwillison.net/tags/ai/)[psf 21](http://simonwillison.net/tags/psf/)
**Previous:**[Qwen3.6-35B-A3B on my laptop drew me a better pelican than Claude Opus 4.7](http://simonwillison.net/2026/Apr/16/qwen-beats-opus/)

### Monthly briefing

Sponsor me for **$10/month** and get a curated email digest of the month's most important LLM developments.

Pay me to send you less!

[Sponsor & subscribe](https://github.com/sponsors/simonw/)

*   [Disclosures](http://simonwillison.net/about/#disclosures)
*   [Colophon](http://simonwillison.net/about/#about-site)
*   ©
*   [2002](http://simonwillison.net/2002/)
*   [2003](http://simonwillison.net/2003/)
*   [2004](http://simonwillison.net/2004/)
*   [2005](http://simonwillison.net/2005/)
*   [2006](http://simonwillison.net/2006/)
*   [2007](http://simonwillison.net/2007/)
*   [2008](http://simonwillison.net/2008/)
*   [2009](http://simonwillison.net/2009/)
*   [2010](http://simonwillison.net/2010/)
*   [2011](http://simonwillison.net/2011/)
*   [2012](http://simonwillison.net/2012/)
*   [2013](http://simonwillison.net/2013/)
*   [2014](http://simonwillison.net/2014/)
*   [2015](http://simonwillison.net/2015/)
*   [2016](http://simonwillison.net/2016/)
*   [2017](http://simonwillison.net/2017/)
*   [2018](http://simonwillison.net/2018/)
*   [2019](http://simonwillison.net/2019/)
*   [2020](http://simonwillison.net/2020/)
*   [2021](http://simonwillison.net/2021/)
*   [2022](http://simonwillison.net/2022/)
*   [2023](http://simonwillison.net/2023/)
*   [2024](http://simonwillison.net/2024/)
*   [2025](http://simonwillison.net/2025/)
*   [2026](http://simonwillison.net/2026/)