pyOpenSci

@pyopensci.org

We build diverse communities that support free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. Join our global community: https://linktr.ee/pyopensci

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

At #PyConUS in Long Beach! Join us TODAY (Fri May 15) 3pm Room 202A for an open space on GenAI & open source. pyOpenSci is actively researching how AI tools are impacting our ecosystem. Come shape the frameworks we're building . All perspectives welcome. #Python #OpenSource

Join us at 2pm friday may 15 in room 202a 
pyOpenSci: ai tools and open source: lets figure this out together.

Community is so critical during times of political unrest. We value the members of the pyOpenSci community who work together to make scientific #opensource more accessible and inclusive and to help researchers and others navigating #python packaging and creating open reproducible workflows.

leah wasser@leahawasser.bsky.social · 10mo ago

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

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

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

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.

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

Turn your scripts into a real Python package! 🐍✨ 📅 pyOpenSci 2-hour workshop: Nov 6, online. ✅ Build a package in minutes ✅ Learn to publish on PyPI ✅ Practice with GitHub Actions 🎟️ Early bird pricing is live now — scholarships are available! 🔗 www.pyopensci.org/events/pytho...

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! Bulleted list: “Build your first Python package; Publish securely to PyPI; Automate releases with GitHub Actions; Write docs that help users & contributors.” Below, event details: Thursday, 6 November 2025, 10:00 AM MST – 12:15 PM MST. Link shown: bit.ly/PythonPackaging. On the right is a simple robot illustration. A teal button at the bottom right says REGISTER NOW.

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

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.

Hot take 🔥 Reproducibility isn’t just about data and methods. It’s about scientific software. If your code can’t be run, your science can’t be trusted. Let’s fix that together. 💜 #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.

Thinking about packaging your Python code, but not sure where to start? 👩‍💻🐍 Our beginner-friendly guide walks you through it step by step: 📂 Organize your code 📝 Write docs ⚙️ Set up pyproject.toml 🤝 Submit for peer review 👉 www.pyopensci.org/python-packa...

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

pyopensci.org