leah wasser

@leahawasser.bsky.social

Executive Director & Founder of @pyOpenSci * open source and open science enthusiast * stravalib & all-contributors bot maintianer * Rescue dog mom * Plant nerd * All things trail, mountain and crossfit * Calisthenics: seeking the perfect bar muscleup.

I'm honored to be a keynote speaker at @europython.eu . 💞 My talk is about seeing through the noise — people, patterns, and intentional AI. Can't wait to bring the @pyopensci.org lens to this stage. I hope to see you there! #EuroPython #Python

EuroPython 2026, Kraków@europython.eu · 3mo ago

Thrilled to announce @leahawasser.bsky.social as a #EuroPython keynote speaker! 🚀 As founder of pyOpenSci, Leah empowers 400+ researchers to build sustainable software. In the age of GenAI, she's protecting the human networks that keep open source alive socially & technically. 🔬💻

Leah Wasser

📣 Join the pyOpenSci editorial team & support software peer review! We're looking for folks with expertise in: 🧬 bioinformatics ⚛️ physics/simulation 📊 sports analytics 🧪 computational chemistry 📈 time-series analysis 🔭 astronomy 🌍 earth science Flexible time commitment, full onboarding. 🐍

Here's alt text for the graphic:

A pyOpenSci call for editors graphic. The top half shows a photo of community members collaborating at a sprint, overlaid with a deep purple tint. Text reads: "Join Our Editorial Team. We need editors with a background in: bioinformatics & genomic surveillance, physics (electron/ion optics), sports analytics & ranking, computational chemistry, time-series analysis, astronomy & astrophysics, earth & climate science." The bottom half has a light cream background with the text "Apply: bit.ly/pyoseditor" and "Questions? Email media@pyopensci.org." The pyOpenSci logo appears at the top.

Celebrate a decade of Research Software Engineering at RSECon26 in Sheffield (9-11 Sep 2026). Registration for in-person & online attendance: now open. Call for Submissions and Call for Reviewers: close Friday 8 May. Don't miss out! edin.ac/3R86Zdr

Logo of RSECon26

I'm honored to be named a Python Software Foundation Fellow! 🐍 This reflects work I started in 2018 with @pyopensci.org —building inclusive pathways for scientists in open source. None of it happens alone. Thank you to 300+ contributors & the broader Python community. #python #opensource #science

Announcing Python Software Foundation Fellow Members for Q3 2025! 🎉

The PSF is pleased to announce its third batch of PSF Fellows for 2025 ! Let us welcome the new PSF Fellows for Q3 ! The following people c...

pyfound.blogspot.com

Pure python packaging feels overwhelming because there are so many tools. But in reality a pure #Python package only needs 3 things (ok 4 - it needs code too to actually run) 🙃 What have been your biggest challenges when trying to package your code? #opensource #openscience #openeducation

pyOpenSci@pyopensci.org · 11mo ago

Your #Python package needs 3 things: ✅ src/packagename directory ✅ pyproject.toml file ✅ unique package name It does NOT need to: ❌ Solve everyone's problems ❌ Be on PyPI immediately If your code helps you, it might help others. Join our workshop for more: Nov 6 💛 bit.ly/pyos-packagi...

Infographic split into two sections. Left side in dark green with checkmark icon titled 'Do's' lists: Create a src/packagename directory, Add a pyproject.toml instead of setup.py, Create a unique package name, Consider submitting your package to pyOpenSci for peer review. Right side in purple with X icon titled 'Don'ts' lists: Don't try to solve everyone's problems, Worry about publishing to PyPI or conda-forge immediately. Bottom text reads 'Embrace the do's, steer clear of the don'ts, and JOIN a community like pyOpenSci for support along the way.' pyOpenSci logo at top. Link at bottom: bit.ly/pyos-packaging-2025

I used to write pages of r scripts to process messy ecological data. Then I learned to package them so others could use and reuse my work! At my first NEON bootcamp, 40+ researchers processed complex data in single lines instead of pages of code. #openscience means more time for discovery. #python

A graphic that says Why Packaging Matters
When I was building the NEON Data Skills program, I had a problem: ecologists weren't trained to handle massive, complex datasets — lidar, hyperspectral imagery, flux towers, time series..

I wrote scripts in R to help researchers parse this messy data (think: huge files with metadata buried deep inside). They worked, but they were pages long and hard to share.

Then a friend suggested I turn my scripts into an R package. With support from the community. I did it.

The difference was instant. When i lead the first NEON Data Skills Boot Camp, over 40 participants processed complex data with single lines of code instead of pages of scripts. Suddenly, we could focus on science, not data wrangling.

That's the power of packaging: one reusable tool can scale learning and impact across an entire field.

Now I'm teaching Python packaging so more researchers can build tools that make getting to the science faster, reproducible, inclusive and collaborative.

pyOpenSci’s vision? 👀 A research ecosystem where the code behind the science is valued as much as the paper. Where collaboration is the norm, not the exception. Where open is the default. 💛

🐍 Want to publish your own Python package? Join pyOpenSci’s 2-hour online workshop Nov 6: ✔️ Build your first package fast ✔️ Learn the core files (pyproject.toml, docs, metadata) ✔️ Publish to PyPI with confidence 📅 Nov 6, 2025 | Online 🎟️ bit.ly/PythonPackaging

Purple graphic with pyOpenSci logo at the top. Large white text reads: From Zero to Python Package. Subheading: A 2-hour packaging workshop with pyOpenSci! A checklist underneath says: Build your first Python package, Publish securely to PyPI, Automate releases with GitHub Actions, Write docs that help users & contributors. Below, text reads: Thursday, 6 November 2025, 10:00 AM MST – 12:15 PM MST. At the bottom: bit.ly/PythonPackaging with a button that says Register Now. A simple robot illustration is on the right side.

🚨 Call for editors! 🚨 We’ve got 3️⃣ new pyOpenSci packages ready for review: ✨ Phyleas (hardware security experiments) ✨ LSAPy (land suitability analysis w/ fuzzy logic) ✨ RSTT (sports simulation w/ probabilistic models) Your expertise could help make scientific software stronger & more reusable.

Purple background with floral illustrations. Text reads: “Get involved with pyOpenSci! We’re growing our editorial team, and are seeking volunteers from a wide variety of scientific backgrounds. Editors: Lead the review process for 3–4 packages a year. Assist with editorial and peer review policies. People from diverse backgrounds are especially encouraged to apply! Questions? Email media@pyopensci.org. Apply: bit.ly/pyOSEditor.” At the bottom are social links: pyopensci.org, Fosstodon @pyOpenSci, LinkedIn pyOpenSci. Illustration shows a person at a desk on a video call with four people.

Did you know? 👀 Every pyOpenSci peer review is collaborative, not combative. Maintainers say that our process leaves their packages stronger, better documented, and more usable...not torn apart. Your code matters. And we’re here to help it shine! ✨ 👉 Learn more: www.pyopensci.org/software-pee...

Welcome to the pyOpenSci Software Peer Review Guidebook!

pyOpenSci is a diverse community that supports the open Python tools that drive open science. GitHub release (latest by date) DOI Learn About Software Peer Review Get a basic overview of our open p...

pyopensci.org

We are thrilled to be working with so many incredible leaders in our #openscience ecosystem. We are collectively thinking about how uniting as nonprofit organizations that care deeply about inclusive and open science can amplify our messages and reach more people.

pyOpenSci@pyopensci.org · last yr.

Open science orgs are stronger together 💪 @carpentries.carpentries.org, OLS, @ropensci.org, @pyopensci.org & @prereview.bsky.social are convening to move from surviving → thriving. Read how we’re charting a sustainable, collective path forward: www.pyopensci.org/blog/pyopens... #OpenScience #FOSS

Logos of the five participating organizations (top to bottom: The Carpentries, PREreview, rOpenSci, OLS, pyOpenSci) enclosed in grey ovals along the border of a larger grey circle. Inside the circle at the top is text in all caps spelling “STRONGER TOGETHER.” Below that is an image of several arms and hands closed in a fist. At the bottom of the image in is text spelling “Building resilience in open science starts with collaboration” with the words “resilience” and “collaboration bolded.

I've used the all-contributors bot for years!! Both at @pyopensci and for stravalib, which I maintain. It's been so fun to help revive the project, learn new tools and get to know and build a new maintainer team 🚀 #opensource is really about people and community at the end of the day.

We are excited for this pure #python packaging workshop!! Our workshops are fun, and you will learn a lot about the packaging ecosystem. We offer scholarships for students and those who have been impacted by recent budget cuts and grant terminations as well. Please share!! #science #opensource

pyOpenSci@pyopensci.org · last yr.

Want your Python code to be installable + reusable? 🐍📦 Join pyOpenSci’s 2-hour workshop From Zero to Python Package (Nov 6). Build your first package, learn PyPI publishing, and automate with GitHub Actions. 👀 See the graphic for registration!

Purple graphic with pyOpenSci logo and text: “From Zero to Python Package — A 2-hour packaging workshop with pyOpenSci.” Bullet points: Build your first Python package; Publish securely to PyPI; Automate releases with GitHub Actions; Write docs that help users & contributors. Event details: Thursday, 6 November 2025, 10:00 AM–12:15 PM MST. URL: bit.ly/PythonPackaging. A “Register Now” button appears at the bottom right. Decorative line-art robot stands on the right side.