StudyDuo
A Python study group takes beginners through the same free Python course at one pace, with a weekly meeting to read and fix each other's code. To find one, start with Python user groups and PyLadies chapters, which run online events, or start your own around a course with a set number of lessons.
Python groups that take beginners now
These were open to newcomers when we checked on November 14, 2026:
| Where | Open to | How it meets | What we saw |
|---|---|---|---|
| Boston Python User Group | "Any topic or expertise level" | A Zoom office hour every other Monday at noon Eastern, plus project nights in Boston | 10,205 members on Meetup; the next online office hour on November 23 |
| PyLadies | Women who code in Python, from newcomers to experienced developers | Local chapters, some with online sessions | About 145 locations listed; the Boston chapter held an online lunch session on November 13 |
| Python Help forum | "All welcome" | Written questions and answers on python.org's own forum | 11,323 topics, 31 of them started in the past month |
Boston's office hour is the easiest way in from anywhere. It's online and unstructured: you can drop in with a question, help someone else, or ask who else is starting a course. Topics can go in the group's #office-hour Slack channel beforehand. PyLadies Boston also co-organizes Boston Python's in-person Project & Collaboration Night, where you don't need a project to come.
Python Discord and the other big coding communities are covered in our coding study group guide. In any chat server or messaging group, keep your phone number and course logins to yourself. In StudyDuo's Find Partners, Python has no interest of its own: filter by Coding, add a country or city, and message the people who fit.
Pick one free course and a pace
Choose the course before the first meeting, so "this week" means the same lesson for everyone. These four are free and start from zero:
| Course | By | Size | Free to use | Good to know |
|---|---|---|---|---|
| Python for Everybody | Charles Severance | 17 lessons | Yes, under a Creative Commons Attribution license | Later lessons cover web services, databases and data visualization |
| CS50's Introduction to Programming with Python | Harvard | 10 weeks and a final project | Yes, through OpenCourseWare | Weekly problem sets, from functions to object-oriented programming |
| Think Python, 3rd edition | Allen Downey | 19 chapters | Yes, online, for noncommercial use | Written for people who have never programmed, or tried and struggled |
| Automate the Boring Stuff with Python, 3rd edition | Al Sweigart | 24 chapters | Free to read online | Later chapters automate files, spreadsheets, PDFs and email |
At a lesson or chapter a week, that's 10 to 24 weeks of meetings. Put the pace in writing at the first meeting, along with the day and time. Free self-paced courses lose most of their learners, and Why Can't I Finish Online Courses? explains why.
A Python study group session for beginners
A session doesn't have to be all writing. Studies of novices suggest that reading code deserves part of the hour too.
Read before you write. Mike Lopez, Jacqueline Whalley, Phil Robbins and Raymond Lister analyzed exam answers from students who had just finished one semester of programming (ICER, 2008). Students who traced code well, or explained it in plain English, also tended to write it well. That's a correlation, not proof that reading causes writing, but both skills fit a group. Explaining code in plain words is close kin to the Feynman technique; tracing means predicting what a loop prints, on paper, before anyone runs it.
Swap Parsons puzzles. A Parsons problem is a working program cut into shuffled lines, sometimes with a wrong line or two mixed in. Barbara Ericson, Lauren Margulieux and Jochen Rick found that solving them took significantly less time than fixing or writing the same code (Koli Calling, 2017). Learning didn't differ significantly, even a week later. Their version also asked students to indent each line, which in Python is part of the syntax. To make one, take your solution, shuffle the lines, remove the indentation and add one wrong line.
Review code against a checklist. Christopher Hundhausen and colleagues added pedagogical code reviews to first-year programming courses at Washington State University (ACM Transactions on Computing Education, 2013). A small team, led by a trained moderator, walks through each other's solutions, checks them against a list of good practices and logs each issue. Across four studies, face to face and online, the reviews improved students' attitudes and their skills in critical review, teamwork and communication. For a first checklist, borrow from PEP 8, Python's official style guide: 4 spaces per indentation level, and lowercase function names with underscores between words.
A 60-minute meeting can follow that order:
| Minutes | What the group does |
|---|---|
| 0 to 10 | Each person explains one function from their week's work in a single plain-English sentence |
| 10 to 20 | Everyone predicts the output of one loop on paper, then runs it |
| 20 to 35 | Members swap Parsons puzzles made from this week's solutions |
| 35 to 55 | One member's code goes through the checklist, and the moderator logs each issue |
| 55 to 60 | Confirm next week's lesson |
The errors your group will meet first
Every Python study group runs into the same few error messages. David Pritchard counted them on CS Circles, a free site with 30 lessons and 100 Python exercises for beginners (PLATEAU workshop, 2015). About 640,000 of its first 1.6 million submissions ended in an error, and five messages led the list:
| Error message | Times |
|---|---|
| SyntaxError: invalid syntax | |
| NameError: name '…' is not defined | |
| EOFError: EOF when reading a line | |
| SyntaxError: unexpected EOF while parsing | |
| IndentationError: unindent does not match any outer indentation level |
By our count, those five made up 62% of all the errors. EOFError is what input() raises when it reaches the end of the input: the program asked for a line that wasn't there. Two others now read differently. Since Python 3.10, released in October 2021, an unclosed bracket is reported where it opens, as "'{' was never closed", and a misspelled name gets a "Did you mean" suggestion.
So have everyone install the same recent version, 3.10 or newer, before the first meeting. Then keep one shared error log with three columns: the message, what caused it, and the fix. The second time someone hits a NameError, the answer is already there.
Between meetings
The meeting is one hour a week, and the lessons happen on the other days. A Python study group can do those days together on StudyDuo, which we make. In Focus Room, open around the clock, the lesson you're on sits under your name while you work on camera, mics off. Study Hour gives the whole group one fixed hour a day, shown in each member's own time zone. A bug that needs talking through is what 1:1 sessions are for: they carry sound, and both people need a verified photo.
A day with 30 minutes in a room counts toward your streak in the app. How the rooms work for a group is on the online study group page.
FAQ
Can we start without installing Python?
Yes, with Think Python: its notebooks run on Colab in the browser. The other three courses expect Python on your own computer.
Can the group's course lead to a certificate?
Some can. CS50P offers verified and professional certificates through edX, and Python for Everybody also runs on Coursera and edX. Check each platform's terms before you pay; the material on the course sites is free.
What if a member already programs in another language?
Python's official tutorial suits them. In its own words, it's "designed for programmers that are new to the Python language, not beginners who are new to programming." Its 16 sections move much faster than a beginners' course.
