Are you a community builder dreaming of bringing EuroPython to your city? The Call for Venues for EuroPython 2026 is now open! 🎉
EuroPython is the longest-running volunteer-led Python conference in the world, uniting communities across Europe. It’s a place to learn, share, connect, spark new ideas—and have fun along the way.
We aim to keep the conference welcoming and accessible by choosing venues that are affordable, easy to reach, and sustainable. As with the selection process in previous years, we’d love your help in finding the best location for future editions.
If you'd like to propose a location on behalf of your community, please fill out this form:
Even if 2026 isn’t the right time, don’t hesitate to get in touch. We'd also like to hear from communities interested in hosting EuroPython in 2027 or later.
Questions, suggestions, or comments? Drop us a line at board@europython.eu—we’ll get back to you!
In March, we achieved two significant milestones alongside several smaller improvements and operational work.
We launched our ticket sales, dedicating substantial effort to setting up the ticket shop, coordinating with multiple teams, and promoting the event.
We also open our call for sponsors, investing considerable time in budgeting, setting up and improving the process, and onboarding our sponsors.
Individual reports:
Artur
Budget projection updates
Ticket launch and related activities.
Sponsor setup update and managing some of the sponsor interactions
Configuration upgrade of our static sever.
Catering negotiations.
Internal discord bot updates.
Financial aid meetings.
Billing flow updates.
Mia
Website: Ticket requirements, PR review, and content updates.
Design: T-shirt review, creation of social media assets for ticket sales and sponsors, and a briefing with a designer.
Budget: Budget proposal.
Sponsors: Cold emailing, sponsor packages, and coordination of the sponsor launch.
Comms: Creation, review, and scheduling of content for the ticket sale launch and call for sponsors; speaker cards; automation proof of concept; International Women’s Day communications; newsletter writing and review; board report; and YouTube videos communications.
PyCon US Booth: Coordination and paperwork.
Grants Program: Communication with recipients.
Venue: Re-signed contract.
Calls with the event manager.
Aris
OPS work, meetings, planning.
Accounting updates.
Billing workflow.
Payments
Ege
Read the Docs previews
Programme API setup.
Implementing a redirection system in the website.
Dependency updates and tailwind migration.
Website: issues and PR reviews.
Shekhar
Financial Aid: Planned how to handle responses and evaluated the process.
Ops: GitHub for task tracking and monitored integrations with team members.
We, the EuroPython Society, were proud partners of Brno Python Pizza. Here’s what they shared with us about the event.
By now, the concept of combining Pizza and Python is well established and documented, it just works! But adding Brno into the mix makes it feel a little bit special for our local community. This was the second Pizza Python in Czechia, following the highly successful event in Prague.
While Prague set a high bar with its buzzing gathering of Python enthusiasts and pizza lovers, Brno brought its own unique flavor to the table, that was definitely no pineapple.
Attendees
We capped the event at 120 attendees — the comfortable maximum for our venue. While we didn’t require attendees to disclose gender or dietary info, we did include optional fields in the ticket form. Based on the responses, we had 99 men and 34 women registered, including both in-person and online tickets. Unfortunately, nobody ticked the box for non-binary or transgender options, which will serve as valuable information for future inclusivity improvements..
We also asked about dietary preferences so we could make sure everyone would be fed and happy. The majority (98) had no restrictions, but we were glad to accommodate 6 vegetarians, 6 vegans, 2 gluten-free eaters, 1 halal, and one “no bananas 🍌”. The last one was the hardest to accommodate because when we called up pizzerias and told them how many pizzas we would like, they thought we were certainly bananas…
The event ran smoothly, with no breaches of the Code of Conduct reported—a testament to the respectful and friendly atmosphere fostered by the community.
The menu
At Brno Python Pizza, we served up a feast sliced into 21 talks on the schedule, several lightning talks and plenty of opportunities to network. Each talk was kept short and snappy, capped at 10 minutes, ensuring a fast-paced and engaging experience for attendees. This is absolutely perfect for us that are having slightly underdeveloped focus glands. Not everyone likes mushrooms on their pizza, neither does everyone enjoy listening purely about AI advances. That’s why we curated a diverse menu of topics to cater to our diverse audience.
Feedback, Things to improve and the Future
From what we’ve gathered, people enjoyed the event and are eager to attend again. They enjoyed the food, talks and that topics were varied and the overall format of the event.
The feedback gathering is also the main thing to improve as we have only anecdotal data. For the next time we have to provide people with a feedback form right after the event ends.
If you ask us today if we would like to organise another edition of Python Pizza Brno, we will say "definitely yes", but we will keep the possible date a secret.
In February, our top priority was event logistics and organizational planning. We worked closely with our event manager, Anežka, on important aspects such as the venue, catering, and other logistics. We're happy to announce that the contract with the venue has been signed!
Another priority was budget planning. Our funding comes from ticket sales and sponsors. We reviewed fixed costs and discussed our strategy for this year. We want to keep the event as affordable as possible to allow more people to attend while also attracting sponsors. At the same time, we need to make sure that the event breaks even and remains financially sustainable in the long term. We also worked on defining sponsorship packages.
The third priority was onboarding the remaining co-leads and teams. Some board members are still involved in specific teams to support new co-leads and other newcomers. We're making sure that everyone has the support and tools they need to contribute.
Individual reports:
Artur
Budget: Discussing different scenarios and overall plan for the budget.
Sponsorship setup: Packages, team meetings and internal sponsorship flow and infrastructure
Updates to the internal discord bot and the community voting app
Community: Attending FOSDEM & Python Pizza Brno
Finaid: onboarding and working out the plan for setup updates for 2025.
Event logistics: Working with Anežka and the rest of the team on various items regarding different providers, contracts and payments.
Mia
Comms & Design: worked on the design brief and budget proposal. Drafted and scheduled some community voting and reviews posts. Reviewed others. Comms & Design team calls. Website design coordination & calls.
Budget: worked on the proposal & spreadsheets.
Sponsorship: helped define sponsorship packages and pricing. Reviewed and helped prepare content for the web and other materials. Coordinated communication between multiple people.
Infrastructure: code reviews.
Community: attended Brno Python Pizza.
Aris
Billing: Setup payments for grants and vendors
Billing: Looked into the current billing workflow and how it can be optimized.
Budget: Onboarding myself to the spreadsheet, looked and discussed the different scenarios
Ops: Onboarding team members, capacity planning and kickoff meeting
Community: Attending FOSDEM & Python Pizza Brno
Ege
Transfer 2025 Discord server ownership to EPS account
22-24 website migration
Website PRs
Program API setup with the new deployment logic
Shekhar
PR for Visa Application process for EuroPython 2025 Conference.
Overviewing Budget sheet for EuroPython 2025 Conference
Overviewing Grant programme and the existing proposals from various conferences.
Finaid team coordination and helped launch the FINAID programme.
The top priority for the board in January was finishing the hiring of our event manager. We’re super excited to introduce Anežka Müller! Anežka is a freelance event manager and a longtime member of the Czech Python community. She’s a member of the Pyvec board, co-organizes PyLadies courses, PyCon CZ, Brno Pyvo, and Brno Python Pizza. She’ll be working closely with the board and OPS team, mainly managing communication with service providers. Welcome onboard!
Our second priority was onboarding teams. We’re happy that we already have the Programme team in place—they started early and launched the Call for Proposals at the beginning of January. We’ve onboarded a few more teams and are in the process of bringing in the rest.
Our third priority was improving our grant programme in order to support more events with our limited budget and to make it more clear and transparent. We went through past data, came up with a new proposal, discussed it, voted on it, and have already published it on our blog.
Individual reports:
Artur
Updating onboarding/offboarding checklists for Volunteers and Board Members
Various infrastructure updates including new website deployment and self-hosted previews for Pull Requests to the website.
Setting up EPS AWS account.
Working out the Grant Guidelines update for 2025
Attending PyConWeb and FOSDEM
Reviewing updates to the Sponsors setup and packages for 2025
More documentation, sharing know-how and reviewing new proposals.
Mia
Brand strategy: Analysis of social media posts from previous years and web analytics. Call with a European open-source maintainer and a call with a local events organizer about EP content.
Comms & design: Call for proposal announcements, EP 2024 video promotions, speaker mentorship, and newsletter. Video production - gathering videos from speakers, video post-production, and scheduling them on YouTube shorts, and social media.
Event management coordination: Calls with the event manager and discussions about previous events.
Grants: Work on new grant guidelines and related comms.
Team onboarding: Calls with potential comms team members and coordination.
PR: Delivering a lightning talk at FOSDEM.
Cyril
Offboarding the old board
Permission cleanup
Team selection
Onboarding new team members
Administrative work on Grants
Aris
Worked on the Grants proposal
Teams selection
Follow-up with team members
Board meetings
Financial updates
Community outreach: FOSDEM
Ege
Working on various infrastructure updates, mostly related to the website.
Reviewing Pull Requests for the website and the internal bot
Working on the infrastructure team proposal.
Shekhar
Timeline: Discussion with the Programme Team, and planning to do the same with the other teams.
Visa Request letter: Setup and Test Visa Request Automation for the current year
The board has been working tirelessly over the past month to bootstrap the organization of the 2025 conference and lead the Society toward a more sustainable and stable future!
In December, we focused on three main areas:
Onboarding
Hiring an Event Manager
Bootstrapping the 2025 conference
Onboarding:
All board members received access to the tools and resources they needed and went through important information in the board wiki to help everyone get started smoothly. We also had 6 board meetings.
Hiring an Event Manager:
This was a big priority and an important step for the future of the Society. We reached out to a candidate and we’re excited that they are interested to cooperate with us! We worked together to define their role, gathered resources for them, and drafted the first version of their contract. We are looking forward to working with them soon!
This is a big move toward making the Society’s future more stable and sustainable.
Bootstrapping the 2025 conference:
In December, we announced that the 2025 conference is happening in Prague. We also have a new website with a new logo. We defined team responsibilities, launched the Calls for Contributors, and promoted it within the EPS, the local community, and on social media. We reached out to our first co-leads to get things moving and currently we are onboarding our first team members.
Individual reports:
Artur
Onboarding new board members - setting up access, sharing resources, setting up the board wiki and documentation
Wrapping up the GA2024, and publishing missing records for GA2023
Setting up the new server for EP websites
Helping with the helpdesk migration
Setting up new infrastructure for EP2025
Coordinating the EP2025 conference launch
Setting up the framework for the Event Manager - responsibilities and the paperwork
Setting up Project Management tools for the Board/2025 Team.
Board Meetings
Mia
Finished all tasks and released videos and materials for GA 2023 and GA 2024.
Went through the board Wiki and onboarded to board resources and tasks.
Scheduled social media posts regarding the conference announcement and informed the local community about it.
Updated the team descriptions document and the Calls for Contributors form, then launched the Calls for Contributors. Announced the Calls for Contributors internally and on social media. Delivered a lightning talk announcing the Calls for Contributors on the local meetup.
Worked on the brand strategy: documented the current state and described personas. Analyzed our media and web presence, attendance data, community voting, and participant feedback. Researched similar-sized conferences for inspiration. Finally, created a 2025 brand proposal for the website and documented everything.
Met with a CPython core developer to brainstorm ideas for the conference, followed by a meeting with the program co-lead.
Reviewed previous venue contract discussions and compared the current contract to the previous one.
Had a call with the event manager, helped define their role in the Wiki, and drafted the first version of the Letter of Engagement.
Scheduled social media posts for the end of the year.
Cyril
Onboarding to the board tasks (getting access, information on the tools used)
Checked the 2024 GA recording for flare ups
Updated the helpdesk instance and other infrastructure tasks
Looked through the old tickets and tried to understand why they are open
Set up part of the environments for the new teams
Helped defining the context for the event manager job
Looked through the old documents and provided cleaned up versions for part of the teams
Prepared the responses from potential conference organisers for the selection
Helped onboard the first Co-Leads
Aris
Onboarding to the board resources and tasks
Helped with the EM responsibilities and scope
Feedback on the call to actions and co-lead recruitment
Updated accounting information with info from the SEB accounts
Board meetings
Ege
Onboarding to the board tasks (getting access, information on the tools used)
Launched the initial website for 2025
Prepared call-to-action cards for the website (for CfC and pre-feedback form)
Discussed the options for the new website/static server/repository structure
Communicated with the PSF Trademarks Committee for the approval of the new logo variations
Had a meeting with a CPython core developer to get feedback and explore ideas to improve EuroPython and EuroPython Society
Discussed ideas for new EuroPython Branding
Shekhar
Worked on EP Timeline Discussion and facilitation
Helped to reach previous on-site volunteers for co-lead recruitment
