About us
This meetup is for anyone with an interest in the Python programming language. We typically have 1-2 talks and a Module of the Month presentation as well as conversation and networking. If you have any interest in Python, please join us!
Code of Conduct
All participants must adhere to the Python Community Code of Conduct. Source: https://www.python.org/psf/codeofconduct/
Python Community Code of Conduct
The Python community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences great successes and continued growth. When you're working with members of the community, we encourage you to follow these guidelines which help steer our interactions and strive to keep Python a positive, successful, and growing community.
A member of the Python community is:
Open
Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise. We're receptive to constructive comment and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference.
Considerate
Members of the community are considerate of their peers -- other Python users. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.
Respectful
Members of the community are respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. We're respectful of the volunteer efforts that permeate the Python community. We're respectful of the processes set forth in the community, and we work within them. When we disagree, we are courteous in raising our issues.
Overall, we're good to each other. We contribute to this community not because we have to, but because we want to. If we remember that, these guidelines will come naturally.
Questions/comments/reports related to CLEpy? Please write to clevelandpython@gmail.com.
Upcoming events
1
ClePy July Meetup - PyOhio Preview!
Happy Dog, 5801 Detroit Ave, Cleveland, OH, USWe will be hosted at Happy Dog, in the Underdog (basement).
Meetup Agenda
6:00-6:30pm Social and Setup, Announcements.
6:30-7:30pm Presentations (see below)
7:30-8:00pm Social and Clean-upWe are excited to preview two talks from PyOhio 2026 . This is an opportunity for you to attend these talks before the conference. It is also an opportunity for the speakers to practice their talks and gather feedback.
Talk 1: My Model Works Locally. Why Is Production Lying to Me?
by Dinky Mishra
You tested it. You validated it. It worked perfectly on your machine. Then you deployed it, and everything fell apart.
Production failures are not random. They follow patterns, and once you know them, you will start spotting them before they cost you a week of debugging. Through a structured walkthrough of real failure scenarios, this talk breaks down the five most common reasons ML models and Python applications behave differently in production than they did during experimentation: training-serving skew, environment mismatches, silent type errors, data assumptions that stop being true, and non-determinism from unseeded randomness.
Each failure mode is paired with a clear diagnosis and a concrete fix you can apply before your next deployment.
Who this is for: Anyone who has deployed a Python application or ML model and been surprised by what happened next. Also valuable for anyone preparing to deploy for the first time.Talk 2: Speeding Up Clinical Trial Analysis with Python
by James Austrow
What do you do when the standard way to solve a problem is just too slow? In any field, comparing pairs of items, whether patients, products, or data points, leads to code that grinds to a halt as the dataset grows. The usual advice? “Just wait longer” or “use a faster language.” But what if you could rewrite the rules?
In this talk, we’ll show how the right algorithm can dramatically speed up a statistical test used in medical research: the win ratio. This method helps doctors and researchers evaluate pairs of patients on complicated criteria, but until now, it’s been painfully slow for large datasets. We’ll break down:- Why the old way is slow, and why most people accept it
- How re-framing the problem led to a smarter solution
- The results: 20-50x speedups for typical trials, and over 100x for huge ones
No advanced math or statistics background required, just curiosity about how Python can solve real-world problems in unexpected ways.
Takeaways:- Learn how algorithmic thinking can turn a slow process into a fast one
- See how pure Python can outperform optimized C++ code in some cases
- Get inspired to look for hidden inefficiencies in your own projects
PyOhio 2026 is on July 25-26 at the Cleveland State University Student Center. Register for free here: https://www.pyohio.org/2026/
---
If you decide to not come to the meetup but initially RSVP yes, please change your response so we have a proper headcount and folks who are on the waitlist can attend.Want to present a talk? Let us know on meetup or the #clepy channel on Cleveland Tech Slack.
Join the Cleveland Tech Slack group here: https://cleveland-tech.vercel.app/
12 attendees
Past events
176
