leah wasser

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...

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

pyOpenSci has a unique, values-driven process in how we select tools that we use in our #openeducation resources, packaging guides and trainings. This process includes bridging diffierent communities that both develop maintain and use these tools. Learn more.

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

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.

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

As a researcher, I learned 2 code the hard way on my own. I wrote messy MATLAB scripts that worked on my computer 😅. No training, just curiosity. I founded @pyopensci.org so people like my former self don't have to struggle alone building #OpenScience workflows. Community matters. Especially now. 💛

A graphic from zero ro Python package. 2 hour packaging workshop. Build a pure Python package using Hatch and UV, publish securely to PyPI, Automate with GitHub actions, and write docs that help users and contributors. Thursday, 6 November 2025. Early bird special is extended. Link: bit.ly/pythonpackaging

🚨 Early bird extended! 🚨
Join our From Zero to Python Package workshop, Nov 6.
Decode the packaging ecosystem: Hatch, PyPI, Uvicorn — and more. Build your package step-by-step. Scholarships available 💛
🔗 bit.ly/pyos-packaging-2025
#OpenScience #Python

Get involved with pyOpenSci pyOpenSci’s Website

So much brilliant work never makes it into a paper.
The code, the data, the long nights helping others debug.
At pyOpenSci, we believe that code, data, and community are the pulse.
Research advances quickly when we build together & openly.
Join us. 💛 bit.ly/pyos-volunteer
#openscience #opensource

They DO!! I actually think typing is a code contribution too!! We had someone join the stravalib team for a while who was super passionate about typing. It was so invaluable to us! And it makes our test suites stronger as new contributions come in. So YES absolutely it all counts and is needed!!

Your #opensource project’s most valuable contributors might never touch code.
I’ve maintained All Contributors Bot for 2 months w/o a line of code—triaging issues, fixing CI, organizing work.
That work keeps projects alive.
What non-code contributions have you made? #science #openscience

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. 💛

Have you ever inherited an #opensource project with limited docs?
I am rebuilding the all-contributors bot and the accounts/workflows r undocumented. I'm becoming a PI in search of accounts 😅

Lesson learned: Create a DEVELOPMENT.md file from day one and add everything to it! #openscience

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.

🐍 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 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.

🚨 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.

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.

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

Our upcoming #python packaging workshop will kick start your packaging journey. This beginner-friendly workshop will take you from 0 to python package in under 5 minutes. From there you will learn about customizing your package, and securely publishing it to PyPI #openscience #opensource

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...

Vaccines work. Period.

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.

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

YouTube video by Stanford Data Science OpenSource@Stanford & pyOpenSci: Improving Research Software through Open and Accessible Peer Review

New collab! OpenSource@Stanford + pyOpenSci hosted their first event on software peer review.

Zach Chandler, @mafrancesca.bsky.social & @leahawasser.bsky.social shared how review helps researchers grow skills, gain recognition & build sustainable Python software.

🎥 www.youtube.com/watch?v=LIE5...

@isabelizimm.bsky.social‬ has been such a guiding light in our @pyopensci peer review process. We are appreciative of her time spent with us as an editor and look forward to continuing to engage with her as a wonderful and knowledgeable community member.

Listening, learning, and building together: what we heard at our SciPy 2025 BoF We held an incredibly informative community session this year at the SciPy meeting in Tacoma Washington. We asked the community what their open source Python pain points were. Learn more about what we...

At #SciPy2025, we asked:

💬 What are your biggest pain points around sharing and maintaining research software?

Attendees answered thoughtfully, honestly, and hilariously (cats 😹).

Here’s what we heard 👇
www.pyopensci.org/blog/pyopens...

#OpenScience #Python #ResearchSoftware

Graphic announcing Eliot Robson as pyOpenSci’s new rotating Editor in Chief for the peer review program. Text reads: ‘THANK YOU Eliot Robson. Eliot Robson is our new rotating Editor in Chief for pyOpenSci’s peer review program. A past package submitter and reviewer, he brings experience and a collaborative spirit to leading our editorial team.’ On the right is a circular photo of Eliot wearing a pastel purple and blue hoodie. The pyOpenSci logo appears at the bottom left.

📢 Eliot Robson is our new rotating Editor in Chief! 🎉

A past package submitter & reviewer, Eliot brings experience and a collaborative spirit to guiding pyOpenSci’s peer review process. 💛

👏 Join us in congratulating him!
#OpenScience #Python #PeerReview #pyOpenSci

I am grateful for the work @tracykteal.bsky.social has put into @pyopensci.org over the past 3 years. It's also exciting to see how much we've grown as an organization. I can't wait to work with @kcranston.bsky.social and April moving forward #openscience #science #opensource #python

Traditional academic peer review can feel harsh.

At pyOpenSci, our reviews are:
🤝 Collaborative
🛠️ Practical
💛 Centered on helping maintainers succeed

Because your code matters and so does the experience of sharing it.

👉 Learn how to submit: www.pyopensci.org/software-pee...

This is a truly powerful report that overviews the profoundly dangerous impacts of GenAI not just on our workflows but also on our lives, our jobs and our livelihoods.

Highlights from SciPy 2025: Building Community, Code, and Culture Explore pyOpenSci’s highlights from SciPy 2025—from Python packaging workshops and talks to first-time contributions, collaboration, and open science in action.

Still thinking about everyone who showed up for open science this month 💛

Contributed to pyOpenSci? We see you.
Curious? We’ve got starter issues + docs to help you begin.

✨ You belong here. Your code matters. ✨

📖 www.pyopensci.org/blog/pyopens...
#pyOpenSci #OpenScience #Python

Graphic introducing pyOpenSci’s first open source infrastructure intern. Text reads: “INTERN SPOTLIGHT. Philip Narteh has joined pyOpenSci as our very first open source infrastructure intern, thanks to the support of Quansight Labs! PHILIP NARTEH.” The image includes a photo of Philip Narteh wearing a white t-shirt that says “WE’RE KIND OF A BIG DEAL,” and the pyOpenSci logo appears at the bottom. The design uses purple tones and rounded shapes.

Thrilled to welcome Philip Narteh as pyOpenSci’s first open source infrastructure intern! 💛

Backed by @quansight.com Labs, Melissa Mendonça & Tania Allard, he’ll help migrate our site to Django—bringing accessibility expertise with him.

👋 Welcome, Philip! #OpenScience #Django #pyOpenSci

pyOpenSci Python Package Guide We support the Python tools that scientists need to create open science workflows. GitHub release (latest by date) DOI new Tutorial Series: Create a Python Package: The first round of our community...

🚨 You don’t need to be a software engineer to contribute to scientific open source!

pyOpenSci welcomes code, docs, ideas, reviews & encouragement 💛

There’s space for you here 🤝

🔗 www.pyopensci.org/python-packa...

#OpenScience #pyOpenSci