Monday, December 03, 2018

November 2018 board meeting summary

On November 12th and 13th, ten of the thirteen PSF board members convened in Chicago, IL. Those who could not make it to the in-person meeting, joined via phone conferencing when possible.

In attendance were Naomi Ceder, Jacqueline Kazil, Thomas Wouters, Van Lindberg, Ewa Jodlowska, Lorena Mesa, Eric Holscher, Anna Ossowski, Christopher Neugebauer, and Jeff Triplett. Kushal Das and Marlene Mhangami connected remotely.

In continued efforts to be transparent with our community, we wanted to share what we discussed and what actions will be taken next.


The first discussion we had pertained to directors' involvement in fundraising.

What is being addressed?

It is common for non-profit board members to help raise resources via their various networks. In the past, our board hasn’t been very active in this area, and we’d like to change that going forward.

What are the next steps?

During the meeting, we created two board committees to get directors more involved in the fundraising process:
  • Fundraising committee: This committee will be focused on incoming sponsorships and donations. Even though this is a responsibility all directors will work on, this committee will help move things forward and provide the resources that other directors need to help with this role.
  • Outreach committee: This committee will decide if/how PSF funds will be used to help promote the PSF globally (this would be in addition to funds given via a grant/sponsorship). This group will also assist with creating resources for directors to use when attending an event to represent the PSF.

Code of Conduct

Since the Code of Conduct’s creation in 2013, the PSF has not updated nor worked on any related resources for our community to use outside of PyCon.

To better support our community, in the third quarter of 2017, the PSF created the Code of Conduct Work Group ( The purpose of this work group is to:
  1. Review, revise, and advise on policies relating to the PSF code of conducts and other communities that the PSF supports. This includes any #python chat community & email list under PSF jurisdiction.
  2. Create a standard set of Codes of Conduct and supporting documents for multiple channels of interaction such as, but not limited to, conferences, mailing lists, slack/IRC, code repositories, and more.
  3. Develop training materials and other processes to support Python community organizers in implementing and enforcing the Code of Conduct.

What is being addressed?

At our November meeting, the board discussed certain risk exposure that was brought to our attention. This discussion is still ongoing and as soon as there is a resolution for moving forward, we will work together with the Code of Conduct Work Group to update the community.

Python in Education

What is being addressed?

At PyCon 2018, one of the directors hosted an open space about Python in Education. The goal was to hear from attendees how the PSF can help educators with any obstacles they face with introducing Python into their curriculums. Lot of data points were collected and needed to be discussed.

What are the next steps?

The board directors created a Python in Education group. This group will facilitate ways the PSF can use its resources to improve the way we support educators with introducing Python into their curriculums.

The first goal will be to curate impactful and proven open source material that educators can use globally. The group will write up a request for proposal, decide on a budget that will be allocated to accepted proposals, and market it to our community. Our intended timeline is to launch the RFP by the new year and have the deadline be before PyCon. At PyCon, we will announce accepted proposals so the work can be done during the third quarter of 2019.

Finance Committee

As the PSF continues to grow, we have to make sure that operationally we are efficient and effective, especially when it comes to our finances.

What is being addressed?

For every non-profit board, a major responsibility is to ensure that there is a group to monitor the organization’s overall financial health. Prior to now, the PSF has not had a board finance committee.

What are the next steps?

During the meeting, we created a committee that the Director of Operations and Finance Controller will report to. To start, the group will meet quarterly. Their goals will be to:
  • Oversee financial planning (PSF & PyCon budgets)
  • Monitor that adequate funds are available for financial management tasks
  • Ensure that assets are protected
  • Draft organizational fiscal policies 
  • Anticipate financial problems from external fiscal environments
  • Oversee financial record keeping
  • Relay financial health to the rest of the board
  • Ensure all legal reporting requirements are met
  • Sustain the financial committee itself by training and recruiting subsequent board members

PyCon Trademark

What is being addressed?

At our meeting in May 2018, the board directors decided that the PSF needs to improve the way we monitor the PyCon trademark. The main reason behind this decision is to protect the mark by being able to prove that we are monitoring its use, which will help avoid certain legal challenges. Additionally, it will help us ensure that all PyCons are up to community standards: Python focused, non-commercial, and have actionable code of conducts.

The process has not yet been fully implemented.

What are the next steps?

The board directors will revive the discussion with the PSF’s trademark committee. The goal is to find common ground on how the process will work. Afterwards, we will work on full transparency with the community via blogs and a message on

Diversity Tracking

Even though this topic was not on our initial agenda, we wanted to talk about this if time allowed. We got lucky and were able to sneak it in!

What is being addressed?

Our grants program currently does not require any tracking or reporting for diversity grants. Nor does the PSF have a policy for expectations of diversity grants. Since we want to see that the funding we give towards diversity is impactful, we wanted to discuss options for what we can do.

What are the next steps?

We will work on a policy for diversity grants that ask organizers to collect relevant diversity statistics. In addition to that, the PSF will work on a template survey so conferences can have a starting point in order to lessen the burden on volunteer organizers. Once a template and policy is in place, we will market the resource via relevant mailing lists, communication chats, and the Grants Program page.

Python Governance and Core Development

Python has recently seen the resignation of its BDFL, Guido van Rossum. This encouraged the core developers to rethink the governance of Python. Several governance proposals were created in the forms of PEPs, which the core developers will be voting December 1st, 2018 to December 16th, 2018 (Anywhere on Earth).

Even though the board is not currently involved with core development, we did discuss what has been developing with the governance discussions. We reflected on some of the discussions happening on We discussed the various PEPs such as PEP 8001, which is about the Python Governance Voting Process. We also discussed what the directors thought about the proposals for Python governance such as PEP 8010, 8011, 8012, 8013, 8014, 8015, 8016.

What’s next?

Working across the table from one another was motivational and acted as a catalyst for several initiatives. It gave us the opportunity to have in-depth conversations, establish stronger professional relationships, and create actionable tasks to help move initiatives forward beyond the two-day meeting.

We plan to host more 24-hour chat channels throughout 2019. They give us the chance to hear from community members world wide. Additionally, we will have our next in-person board meeting at PyCon 2019 on May 2nd. We look forward to updating you all on our progress then.

It is important for us to know that the PSF Board is inline with our community’s needs. If you have comments or suggestions on what was recently discussed or something completely new, please reach out to me: ewa at python dot org.

Monday, November 19, 2018

PyPI Security and Accessibility Q1 2019 Request for Proposals period opens.

The Python Software Foundation Packaging Working Group has applied for and received a commitment from the Open Technology Fund to fulfill a contract via their Core Infrastructure Fund.
The Python Package Index (PyPI) is a foundational component of the Python ecosystem and broader computer software and technology landscape. This project aims to improve the security and accessibility of PyPI for all users worldwide, whether they are direct users, like project maintainers and pip installers, or indirect users. The impact of this work will be highly visible and improve crucial features of the service.
We plan to begin the project in January 2019. Because of the size of the project, funding has been allocated to secure one or more contractors to complete the development, testing, verification, and assist in the rollout of necessary features.


2018-11-19Request for Proposal period opens.
2018-12-14Request for Proposal period closes.
2018-12-21Date proposals will have received a decision.
2019-Q1Contract work commences.

What is the Request for Proposals period?

A Request for Proposal (RFP) is a process intended to allow us (The Python Software Foundation) to collect proposals from potential contractors and select contractor(s) best suited to fulfill the specified work.
After the RFP period closes we will evaluate the received proposals based on the evaluation criteria, seek clarification from proposers as necessary, and select one or more contractors to complete the work specified in the scope.
The Request for Proposals period opens today, November 19th, 2018, and is scheduled to close December 15, 2018 AoE.

How do I submit a proposal?

First, please read the full contents of the Request for Proposals here!
You'll find the instructions for submission, evaluation criteria, as well as scope of the project there.

Tuesday, October 30, 2018

PyPI Security and Accessibility Q1 2019 Request for Information period opens.

The Python Software Foundation Packaging Working Group has applied for and received a commitment from the Open Technology Fund to fulfill a contract for their Core Infrastructure Fund.
PyPI is a foundational component of the Python ecosystem and broader computer software and technology landscape. This project aims to improve the security and accessibility of PyPI for all users worldwide, whether they are direct users like project maintainers and pip installers or indirect users. The impact of this work will be highly visible and improve crucial features of the service.
We plan to begin the project in January 2019. Because of the size of the project, funding has been allocated to secure one or more contractors to complete the development, testing, verification, and assist in the rollout of necessary features.
Register Interest
To receive notification when our Request for Information period closes and the Request for Proposals period opens, please register your interest here.

What is the Request for Information period?

A Request for Information (RFI) is a process intended to allow us (The Python Software Foundation) and potential contractors to openly share information to improve the scope and definition of the project at hand.
We hope that it will help potential contractors better understand the work to be completed and develop better specified proposals. Additionally we hope that the open nature of our RFI will expose the project to multiple perspectives and potentially help shape the direction for some choices in the project.
The Request for Information period opens today, October 30, 2018, and is scheduled to close November 13, 2018.
After the RFI period closes, we will use the results of the process to prepare and open a Request for Proposals to solicit proposals from contractors to complete the work.

More Information

The full version of our Request for Information document can be found here.


Our RFI will be conducted on the Python Community Discussion Forum. Participants will need to create an account in order to propose new topics of discussion or respond to existing topics.
All discussions will remain public and available for review by potential proposal authors who do not wish to or cannot create an account to participate directly.

Monday, October 22, 2018

2018 PSF Recurring Giving Campaign

The PSF is launching an end-of-year fundraising drive to build a sustainable community of supporters. Our goal is to raise $30,000! You can help by signing up to give monthly or if you’re already a supporting member (Thank You!!), by checking the box to renew your membership automatically.

The drive begins October 22 and concludes November 21, 2018.

Your donations have IMPACT

Over $118,543 was awarded in financial aid to 143 PyCon attendees in 2018.
$240,000 has been paid in grants from January through September 2018 to recipients in 45 different countries.

Some examples of how your donation dollars are spent:

  • $35,000 was provided to the Python Core Development Sprint in 2018
  • $20,000 helps support 11 Python conferences, impacting over  3,000 people globally
  • $20,000 helps support ~25 hands-on workshops impacting over 700 people 
  • $10,000 supports user group meetup fees for 150 groups for 6 months
  • $5,000 provides hosting for 3-4 PSF community web services for a year(e.g.,,
  • $1,000 helps supports 2 regional conferences, impacting over 500 people
  • $50 supports a Python meetup group for 3 months

This work can’t be done without the generous financial support that people like you provide.

It's easy to donate - 

  • Click here to make a one-time or recurring donation.
  • If you’re an existing PSF Supporting Member and would like to make your support recurring, log into your account and click “Auto-Renewal”.
  • If you’re an existing Supporting Member and would like to support the PSF beyond your $99 annual fee, use this donation page to select an additional one-time or monthly donation.
  • If you'd like to join the PSF, click here to become a Supporting Member and optionally make a one-time donation.
 More details on contributing can be found on the 2018 PSF Recurring Giving Campaign page.

Thank you to everyone who has contributed to our past fundraisers! Your support is what makes the PSF possible and is greatly appreciated by the Python community.

If you would like to share the news about the PSF’s Recurring Giving Campaign, please share a tweet via this tweet button or by copying the text in the following:

Contribute to our Recurring Giving Campaign & help us reach our goal of $30K. The PSF is a non-profit organization entirely supported by its sponsors, members & the public. #idonatedtothepsf #ijoinedthepsf

Wednesday, October 10, 2018

Python Software Foundation Fellow Members for Q3 2018

We are happy to announce our 2018 3rd Quarter Python Software Foundation Fellow Members: 

Stefan Behnel

Blog, Github
Andrew Godwin
Website, Twitter
David Markey
Eduardo Mendes
Github, Twitter, LinkedIn
Claudiu Popa

Congratulations! Thank you for your continued contributions. We have added you to our Fellow roster online.

The above members have contributed to the Python ecosystem by maintaining popular libraries/tools, organizing Python events, hosting Python meet ups, teaching via YouTube videos, contributing to CPython, and overall being great mentors in our community. Each of them continues to help make Python more accessible around the world. To learn more about the new Fellow members, check out their links above.

If you would like to nominate someone to be a PSF Fellow, please send a description of their Python accomplishments and their email address to psf-fellow at Here is the nomination review schedule for 2018:

  • Q4: October to the end of December (01/10 - 31/12) Cut-off for quarter four will be November 20. New fellows will be announced before December 31. 

We are looking for a few more voting members to join the Work Group to help review nominations. If you are a PSF Fellow and would like to join, please write to psf-fellow at

Thursday, October 04, 2018

Join the 2018 Python Developers Survey: Share and learn about the community

2018 is drawing to a close and we are excited to start the official Python Developers Survey for 2018!

In 2017, Python Software Foundation together with JetBrains conducted an official Python Developers Survey for the first time. Over 9,500 developers from almost 150 different countries participated to help us map out an accurate landscape of the Python community.

With this second iteration of the official Python Developers Survey, we aim to identify how the Python development world looks today and how it compares to last year. The results of the survey will serve as a major source of knowledge about the current state of the Python community, so we encourage you to participate and make an invaluable contribution to this community resource. The survey takes approximately 10 minutes to complete.

Please take a few minutes to complete the Python Developers Survey 2018!

Your valuable opinion and feedback will help us better understand how different Python developers use Python, related frameworks, tools, and technologies. We also hope you'll have fun going through the questions.

The survey is organized in partnership between the Python Software Foundation and JetBrains. After the survey is over, we will publish the aggregated results and randomly choose 100 winners (those who complete the survey in its entirety), who will each receive an amazing Python Surprise Gift Pack.

Tuesday, September 25, 2018

CPython Core Developer Sprint 2018

This September, twenty-nine core committers arrived at Microsoft’s main campus in Redmond, Washington, USA for the now-annual core developer sprints. These are an opportunity for the core team to have focused discussions, in-depth conversations and work free from interruption for five days. By the end of the week, thirty-one core developers went home tired but satisfied.

The major sponsor of the sprints this year was the Python Software Foundation. Microsoft provided the venue and some events during the week, and Facebook, Microsoft, Google, LinkedIn, Bloomberg, and a number of small companies covered their employees’ expenses.

Major Achievements

With over thirty people working for a week, there were many achievements and improvements made for Python 3.8 and earlier versions. Some of the highlights include:

  • The asyncio documentation was completely rewritten
  • Most of PEP 572 (assignment expressions) was implemented and tested
  • Recursive tracebacks and syntax errors in f-strings were improved to provide better feedback
  • The Automerge bot was enabled on the CPython GitHub repository, helping reduce the amount of manual work done by core committers
  • importlib_metadata was improved, helping to standardize the way Python exposes information about installed packages
  • The zipimport module was rewritten in Python code, which will enable new development and improvements for importing modules directly from ZIP files
  • Over 45 contributions (besides our own) were reviewed and merged, and over 80 issues were closed in the CPython repository, with many others in related projects such as Buildbot, Roundup, blurb, and our GitHub bots

Governance Discussions

With our BDFL of Python retiring earlier this year, we spent some time discussing how to approach the future of Python. More than any specific outcomes, the discussions were very fruitful and helped many of us see how similar our positions are to each other.

While no decisions have been made, all current proposals intend to keep the PEP process, and limit the new leaders’ responsibilities to arbitrating controversial decisions.

Final proposals are due by the end of September. See PEP 8000 for an overview of the process and links to related PEPs.

New Core Developers

Those who read the first paragraph carefully will have noticed that more committers left the sprints than arrived. This happened because we appointed two new core developers during the week. Congratulations to Emily Morehouse and Lisa Roach!

From Raymond Hettinger’s announcement post:
Emily is the Director of Engineering at Cuttlesoft. She has previously attended two Language Summits and three core development sprints at PyCon. Since July, Emily has worked with Guido's guidance to implement PEP 572, Assignment Expressions.  She has also worked with Eric Snow to dive into CPython's runtime as well as subinterpreters.  This year at PyCon she gave a talk on Python's AST.
Lisa has a background in network engineering and supported the Cisco sale engineer team to develop high quality Python product demonstrations.  Later she moved to the Facebook security team.  This is her third core developer sprint.  She and Guido are co-authors of PEP 526, Syntax for Variable Annotations. Last year, she worked with Eric Smith on PEP 557, Data Classes.

Other Blogs

Other attendees have posted their own blogs describing their experiences at the sprints. (This list may be updated over time as more are published.)

Thank you!

A huge thanks to all the participants who attended, the various companies who sponsored parts of the event, and the PSF for covering the majority of travel expenses. Thanks also to those contributors who were unable to make it this year. Hopefully next year we can include even more core contributors.

Attendees: Brett Cannon, Kushal Das, Ned Deily, Steve Dower, Ethan Furman, Larry Hastings, Christian Heimes, Raymond Hettinger, Łukasz Langa, Ezio Melotti, Emily Morehouse, Benjamin Peterson, Davin Potts, Lisa Roach, Pablo Galindo Salgado, Neil Schemenauer, Yury Selivanov, Eric V. Smith, Gregory P. Smith, Nathaniel Smith, Eric Snow, Victor Stinner, Andrew Svetlov, Guido van Rossum, Dino Viehland, Petr Viktorin, Zachary Ware, Barry Warsaw, Mariatta Wijaya, Carol Willing

Written by: Steve Dower

Tuesday, August 28, 2018

Redesigning the Python Package Index

In April this year a new version of the Python Package Index (PyPI) was released, an effort made possible by a generous award from the Mozilla Open Source Support program.

A major change in PyPI is the new user interface - something that had not seen any sizeable updates for over ten years. Understandably there have been questions about what’s next for the new UI, which as the designer of Warehouse (the project powering PyPI), I would like to address.

The PyPI homepage

The new design

PyPI’s new design is a reflection of the Python community - modern, welcoming and inclusive.

The design emphasises inclusion by providing extensive help documentation, user friendly interfaces, accessible font sizes and a high-contrast color scheme. The entire site works across all resolutions, meaning that you can now use PyPI on any device.

These features are no accident, as the goal of the redesign is to make PyPI a success for as many users as possible. This a big challenge as over 15 million people from 236 different countries visit each year (Aug 2017 - July 2018).

While the new design is informed by usability standards and user experience best practices, it’s now time to take PyPI to the next level: informing design improvements by engaging in community research and user testing.

Next steps

The first area we are looking to improve is the project's detail page (view example), which is - as the name suggests - the page where the details of a particular project can be viewed.

This is by far the most visited page type on PyPI. In July 2018 alone, 76.59% of page visits were to a project detail page, or 3,594,956 visits from a total page visit count of 4,693,561. The majority of users arrive on these pages direct from Google or other sources, bypassing the PyPI home and search pages.

Given these numbers, even a small improvement in the efficiency of this page would return great results for the community. The question is: how should we decide what to change? What one user might think of an improvement, others may consider a regression.

Conducting user research

In an effort to better understand what our users want from the aforementioned page, we ran a design research exercise (full writeup) asking Python community members to rank the importance of different pieces of information on the page. 1,926 people participated in the exercise. These were the results:

From this research, we can ascertain that many users highly value the project description, information about the required version of Python, and links to the project online. In contrast, few users value the trove classifiers, list of maintainers, or instructions on how to see statistics about the project.

Such insights are essential in driving the redesign in a way that prioritises important information for the largest number of users.

Running user tests

In conjunction with this research we are also establishing a user testing program, where PyPI users will give their feedback to the team via a remote video call; answering specific usage questions or completing certain tasks on the site.

Our goal is to run these sessions with a diverse group of users, accounting for the different people, places and ways that Python is used, while establishing major “pain points” with the current design. From this, we can open issues in the issue tracker to address problems, as has happened before with previous rounds of user tests conducted on the project management interfaces.

User tests can also be used to test new design concepts, compare the performance between old design vs new proposals, and ascertain if the proposed design solutions are truely performant.

Help us help PyPI!

So - how can you help us take PyPI to the next level?

If you’d like to participate in user tests, please register your interest. Depending on your profile and availability, we will be in touch to organise a testing session.

If you have a background in design/research or are interested in facilitating user tests, please contact me on All help is welcome!

We appreciate new contributors to the Warehouse project, with reserved issues for new contributors and love donations to the Python Packaging Working Group as these help us build a more sustainable model for Python packaging.

Finally, if you are interested in participating in future rounds of user research, please follow PyPI on Twitter or keep an eye on for future announcements!

Thursday, August 23, 2018

PyCon 2019 - Call for Sponsors

It seems like PyCon 2018 was just last week, but the 2019 edition will be here before we know it. We want to say thanks to all our sponsors who helped make the conference a huge success. This year, we welcomed 3,260 attendees from 48 different countries around the world, strengthening the connection in our beloved community even more. 
The invaluable and generous support of our PyCon sponsors enables the Python Software Foundation to help and improve the Python community worldwide by promoting sprints, meetups, events, projects, fiscal sponsorships, software development, open source projects and the Python Ambassador Program – which helps the creation of communities where Python is not well known. 
PyCon sponsorship enabled us to award $118,543 USD in financial aid to 143 attendees in 2018. It also generates 80% of the PSF's revenue, making financial aid, conferences, workshops, and training support possible. As a result, in 2017 $271,138 was awarded to grant recipients in 34 different countries and we are on track to meet or beat our total from last year.
Your sponsorship helps keep PyCon affordable and accessible to the widest possible audience. 
Here is a sample of the many benefits from being a sponsor:
  • Being part of the biggest Python conference in the world
  • Visibility to those who could potentially become new customers or employees
  • Increasing your brand exposure and elevating your corporate identity within the community
  • Expose your products to more than 3,200 attendees
  • Enhance your company’s reputation by supporting and investing in Python and the open source community
Depending on your level of sponsorship, packages may include complimentary conference passes, booth space, lead retrieval scanners, speaking opportunities, and participation in the Job Fair. Our current sponsorship prospectus can be found here. Sponsors in the Diamond, Platinum, Gold or Silver categories will receive additional tickets to the conference.
We want to hear from you! Contact us anytime - we are flexible and willing to build a sponsorship package that fits your needs. Only you know your business, how you measure success and what you're looking for. For more information please contact or
We proudly want to announce the organizations that are already sponsoring the PyCon 2019!
Huntington Convention Center - Cleveland, Ohio.
Photo Credit: Mike Pirnat
PyCon 2019 will be held at Huntington Convention Center in Cleveland, Ohio, from May 1st to May 9th.
If you would like to share information about PyCon 2019 sponsorship, please share with this tweet:
Support @ThePSF by sponsoring @pycon 2019! More information can be found here: #pycon2019

PyCon 2018 Staff.
Photo Credit: Mike Pirnat

Here’s what our attendees say about the PyCon US experience:

#PyCon2018 was my first PyCon. I have had an INCREDIBLE time! I've listened to inspirational speakers; met some of the most amazing people and have made lifelong connections. Most of all, I had FUN! Thanks to the brilliant @pycon team for working tirelessly to make it a reality!
- Julian Sequeira (@_juliansequeira)

PyCon has been my gold standard for conference accessibility as long as I've been attending, they do a great job and the community here really reflects it. I appreciate all your hard work @pycon, keep it up.
- Jonan Scheffler (@thejonanshow)
#pycon2018 was incredible. The support and hospitality from #Cleveland was stellar. Lighting all the downtown buildings in blue and yellow was a class act. I can’t wait to come back next year for some Mabel’s BBQ and the amazing @pycon community
- Jenn Basalone (@pennyblackio)
One of more understated benefits of @pycon is the economic and social impact in the surrounding communities it takes place at. In the case of larger cities, might not a big deal. In smaller locales, like Cleveland, that impact can be huge!
- Ruben Orduz (@rdodev)
Just got back from @pycon. Was delighted by the inclusiveness and thoughtfulness I saw there.
- David Vandegrift (@DavidVandegrift)

Rock and Roll Hall of Fame - Cleveland, Ohio
Photo Credit: Mike Pirnat
PyCon is underwritten by the Python Software Foundation, a 501(c)3 charitable organization set up to manage the growth and development of Python worldwide.

Thursday, July 26, 2018

The PSF Jobs Volunteer Team: Community Service Award Q1 2018 Recipient

The popularity of the Python language has increased exponentially in recent years. Notably, Stack Overflow highlighted Python as the fastest growing major programming language. As Pythonistas, we know why: Python is easy to learn, solves real world problems in a variety of fields, and has an amazingly friendly community.

With its success, companies around the world are using Python to build and improve their products, creating a growing need for people that know – or are willing to learn – the language. Today you can see Python’s popularity reflected in the growing supply of Python-related jobs with a quick internet search. Or you can head over to the the Python official site and look at the Python Jobs board! Created in 2010 as a way to connect developers and companies, the Python Jobs board was relaunched in early 2015 and has since been run by an awesome team of volunteers.

It’s with great pride that the Python Software Foundation has awarded Jon Clements, Melanie Jutras, Rhys Yorke, Martijn Pieters, and Marc-Andre Lemburg with the Q1 2018 Community Service Award:
RESOLVED, that the Python Software Foundation award the Q1 2018 Community Service Award to the following members of the PSF Jobs Volunteer Team for the many hours they have contributed to reviewing and managing the hundreds of job postings submitted on an annual basis: Jon Clements, Melanie Jutras, Rhys Yorke, Martijn Pieters, and Marc-Andre Lemburg.

PSF Jobs Volunteer Team: A Team of Dedicated Volunteers

As a job poster, all you need to do is register on the Python website and create a job posting filling out the required information. Then, the Jobs Volunteer Team will review them one by one against a list of criteria – such as text format, the job description and how it is related to Python. The entry can be automatically published or sent back to its author with a review note. The process may seem simple, but imagine doing that for hundreds of jobs each year - that's a lot of responsibility!

The PSF Jobs Volunteer team has five members, including members Marc Andre and Rhys York.

Marc-Andre is the CEO and founder of, a Python-focused project and consulting company based in Germany. He has a degree in mathematics from the University of Düsseldorf.
His work with Python started in 1994.

As a Python Core Developer, Marc-Andre designed and implemented the Unicode support in Python 2.0, and authored the mx Extensions. He is also the EuroPython Society (EPS) Chair, a Python Software Foundation (PSF) founding Fellow and co-founded a local Python meeting in Düsseldorf (PyDDF). He served on the board of the PSF and EPS for many terms and loves to contribute to the growth of Python wherever he can.

Rhys grew up in a small town in Ontario, Canada where he developed a passion for drawing, writing and technology.

He began working in 1999 on Marvel Comics' Deadpool, and since that time has had the opportunity to work on ThunderCats, G.I. Joe, Battle of the Planets, and a number of exciting properties. He works in the film, television and video game industries - notably on Funcom’s "The Secret World", Drinkbox’s "Tales from Space: About a Blob" and Ubisoft's "FarCry 5".
Rhys recently wrapped on the third season of the science-fiction television series "The Expanse" as well as on the film "Polar". Rhys is also currently working as Art Director at Brown Bags Films on an undisclosed animation project. As if that wasn’t enough, Rhys teaches Python to children and adults as well. Rhys is very passionate about promoting programming literacy.

Engagement, Challenges and the Future of the Python Job Board

Explaining his involvement with the PSF Jobs Volunteer Team, Marc-Andre says,

“I took over the Job Boards project after the previous maintainer, Chris Wither, left the project in 2013. I kickstarted the relaunch project in February 2014 to migrate the old job board to the new platform.  
The project was on hold for several months between August 2014 and January 2015, but then picked up speed again and we were able to relaunch the Job Board on March 19th 2015. 
Since then a team of reviewers has been working hard to keep up with the many job postings we get each day.”

The Jobs Team faced several challenges during the platform redesign, such as managing the project, rethinking the review process, and finding people to help and. Following the relaunch the team faced additional challenges in keeping up with processing all the job posts that were remaining in the backlog.

As for the future of the Team, Rhys wants to continue providing a service to the Python community and Marc-Andre has worked with the PSF to turn the group into a PSF Working Group as of July 24, 2018. This change will enable to group to get more recognition from the PSF and the Python community at large.

How you can get involved

If you want contribute and be a part of the Team, Marc-Andre says:

Today, the job reviews are pretty easy to manage. We have laid out a set of rules which work well and reviews don't take long to do anymore. The process is documented here.

There are still a few rough edges in the system, so if there are Django programmers willing to help, please get in contact with Berker Peksağ and submit Pull Requests for the open issues we have on the tracker.

Rhys adds, “Do it. Even if you have little time, giving back to the community is a rewarding experience.”

Marc-Andre, member of The PSF Jobs Volunteer Team 

Wednesday, July 18, 2018

The Happy Medium: Distinguished Service Award Winner Tim Peters

When Tim Peters started working on Python, his first advice for Guido van Rossum was that programmers want to add ints and floats. From the beginning, Python had both kinds of numbers, just like today, but adding them together then required a cumbersome type-cast. Peters argued that Python should implicitly convert ints to floats, like most other languages, for programmers' sake: "That is a very common operation for anyone who works with floating point numbers," Van Rossum recalls him saying, "so you’ve got to do it this way."

Ever since, Peters has pushed the language in this direction. He insists that Python should be a practical language that caters to the needs of programmers, and he has a knack for guiding design debates to achieve this goal. In recognition of his contributions, the PSF presented Tim Peters with the 2017 Distinguished Service Award.

A Realist Algorithm

"Timsort is Tim's grand opus," says Van Rossum. The algorithm is not only the standard sort for Python; when Java developer Joshua Bloch saw its merit for sorting real-world data, he incorporated it into the Java standard library as well. The genius of Timsort is to recognize how data naturally occurs in everyday programs: it's less likely to be randomly ordered than to be partly ordered, or ordered in reverse. Programmers usually throw such data at a sorting function anyway, and a theoretically elegant algorithm like Quicksort won't recognize the shortcuts it could take to save work. Timsort is designed to recognize such opportunities and deploy efficient tricks for them.

Timsort is optimized for the world not as we imagine it, but as it is. This realism is characteristic of the Python language as a whole. It flows from Van Rossum's taste in design, which Peters distilled into a poem in 1999.

The Zen of Python

It's only 19 lines. But this short list of precepts has influenced the language and the programs written in it profoundly. It is a shared literature for Python programmers, in the same way that most English speakers know certain lines of Shakespeare. Python's designers quote the Zen of Python in PEP debates, and programmers reviewing code in their own Python projects use the Zen to support their opinions.

Guido van Rossum says, "You can use it to motivate a design choice, but it’s not scripture. It can’t be the only reason to choose a particular design. You still have to put your thinking cap on." Just like the Zen Buddhist sayings that inspired it, Peters's text isn't dogma. Indeed, for every commandment the Zen of Python hands down, there is also a joke or a contradiction to remind us to take it lightly.

Core developer Carol Willing summarizes the Zen of Python's message like this: "We're going to meet constraints in a way that makes good common sense first, so you can maintain the code and people can understand the code." It's this commonsense approach that makes Python a joy to use. Willing began coding on a mainframe at Bell Labs when she was in fifth grade in 1976; in all her years as a programmer the most enjoyable have been her years with Python. She says, "Every day I get to use it makes me feel like a kid again." Now, when she teaches Project Jupyter interns each summer, one of her first instructions is to type "import this".

Willing extends Python's Zen to its community, too. She says that "Beautiful is better than ugly" is a good guide for talking with our colleagues. "There’s an ugly way of saying things, and a more respectful, nicer way of saying things. Maybe we should err on the side of being respectful and nice."

A Happy Medium

In Guido van Rossum's estimation, Peters's biggest contribution to the community has been his years of answering questions and guiding debates on the Python mailing list, writing each message precisely and cheerfully. PSF director Thomas Wouters agrees: "Tim is just never flustered. He always takes it in good humor and it definitely has an effect on everyone else, as well." Even an experienced developer like Carol Willing says that when she sees a post from Peters on a topic she knows, she'll take the time to read it for new insights or new ways of explaining.

In design debates, Peters invented a notion of "channeling Guido" to free Van Rossum from the overflow of emails. He claimed to act like a spirit medium speaking with Van Rossum's voice, but this understates Peters's influence. "He was a mentor for me," says Van Rossum. "He combines incredible technical skills with insight into what the person he's communicating with is missing or needs to see, with a patient way of explaining. He showed me that style of communicating which I strive for but can't always do."

Recently, in the wake of contentious debate over the ":=" operator, Guido van Rossum resigned as BDFL. Tim Peters, too, is less active on Python mailing lists than before. The Python community can no longer rely on one individual and his channeler for guidance. As Brett Cannon wrote, "a key asset that Guido has provided for us as a BDFL is consistency in design/taste." As a summary of Van Rossum's thinking, the Zen of Python is now more important than ever.

Images: Utagawa Kuniyoshi (1797-1861), 108 Heroes of the Popular Suikoden.

Thursday, July 05, 2018

Ophidia in Urbe - PyLondinium Arrives

Latin scholars will tell you that “Ophidia in Urbe,” the tag line for PyLondinium (London, June 8-10), is Latin for “Snakes in the City”.

The snakes, of course, are Pythonic and “the city” is the City, the banking district of London, specifically Bloomberg’s new European headquarters, just across the way from the Bank of England. It’s a beautiful building and it contains the carefully excavated and reconstructed remains of a 3rd century Roman temple to Mithras. Ergo (as those Romans would say) the need for a Latin tagline.

But what’s really distinctive about PyLondinium is the whole idea behind it. PyLondinium was intended to be a small conference that 1) offered great talks, 2) had a very affordable ticket price, and 3) raised a reasonable amount of money for the benefit of the PSF and its programs around the world. And all of this in London, one of the more expensive cities in the world. 

With the London and UK Python community at hand, getting great talks was the easy part. Keeping prices low and still raising money for the cause was a harder problem.

Founder and chair of the conference, Mario Corchero, had an answer to that problem. One of several Bloomberg employees also involved in the Python community, Mario was also the chair of last year’s PyCon España (and co-chair of the PyCon Charlas track), and several other Spanish employees of Bloomberg London had been on the PyConES organizing team. The inspiration of Mario and his team was to combine their own organizing experience with Bloomberg’s sponsorship, which provided the venue and the food. 

The result was a strong first time conference - selling 270 tickets, with 2 days of talks preceded by a day with a dateutils sprint, a PyLadies tutorial, and a Trans*Code hackday, in the heart of London, all for a standard ticket price of only £35. Even better, to support diversity anyone attending the PyLadies or Trans*Code events (both free) also got a free ticket to the main conference if they wanted. Feedback from attendees was overwhelmingly positive, and PyLondinium looks poised to build on that success in the future. 

And what about raising money for the PSF? Yes, PyLondinium did a great job with that as well, sending $14,000 to the PSF to support Pythonic communities and activities around the world. 

Thank you from the PSF, and well done, you!

Friday, June 29, 2018

Python Software Foundation Fellow Members for Q2 2018

We are happy to announce our 2018 2nd Quarter Python Software Foundation Fellow Members:

Anthony Shaw

Twitter, GitHub, Website
Christian Barra
Twitter, GitHub, Website
Jeff Reback
Twitter, GitHub
Joris Van den Bossche
Twitter, Github, Website
Katie McLaughlin
Twitter, GitHub, Website
Marc Garcia
Twitter, LinkedIn, GitHub
Rizky Ariestiyansyah
Tom Augspurger
Wes McKinney
Twitter, GitHub, Website
Yury Selivanov
Twitter, GitHub, Website

Congratulations! Thank you for your continued contributions. We have added you to our Fellow roster online.

The above members have contributed to the Python ecosystem by maintaining popular libraries, organizing Python events, hosting Python meet ups, teaching classes, contributing to CPython, and overall being great mentors in our community. Each of them continues to help make Python more accessible around the world. To learn more about the new Fellow members, check out their links above.

If you would like to nominate someone to be a PSF Fellow, please send a description of their Python accomplishments and their email address to psf-fellow at Here is the nomination review schedule for 2018:

  • Q3: July to the end of September (01/07 - 30/09) Cut-off for quarter three will be August 20. New fellows will be announced before end of September. 
  • Q4: October to the end of December (01/10 - 31/12) Cut-off for quarter four will be November 20. New fellows will be announced before December 31. 

We are looking for a few more voting members to join the Work Group to help review nominations. If you are a PSF Fellow and would like to join, please write to psf-fellow at

Thursday, June 28, 2018

Dr. Russell Keith-Magee, the Python Warrior: Community Service Award Q4 2017 Recipient

Dr. Russell Keith-Magee known name in the Python community having developed with Python since the late 1990s starting with Python version 1.5.

Russell started his career coding with Perl but was confused with it’s design philosophy of TMTOWTDI ("There’s More Than One Way To Do It”). This ultimately led Russell to Python. With its minimal use of symbols in it’s syntax - preferring keywords instead - and mandated indentation, Python was “a breath of fresh air”. Russell recalls, “I found myself wanting to use Python for more and more as time went by”. Contrasting Perl’s TMTOWTDI philosophy to Python’s “there should be one - and preferably only one - obvious way to do it” philosophy was a much welcomed change

Russell was elated to discover Python’s broad range of use cases. As he describes, Python “is used for systems integration, to run websites, to statistical data analysis, to predict astronomical phenomena, i
t's used for educating people who are just learning to program, and it's used by experienced programmers for serious heavy lifting". Such breadth of usage gives Python its most incredible aspect -- a diverse user community. “We should always remember that we are a community. Communities depend on people being involved, and giving back when they can.” 

Gallant Sir Russell, The Victorious Knight

Like Russell, we at the Python Software Foundation share the love for our Python community. We are delighted have such selfless and community minded Pythonistas in our ranks. Therefore the Python Software Foundation is honored to present the 4th Quarter Community Service Award for 2017 to Dr. Russell Keith-Magee:

RESOLVED, that the Python Software Foundation award the Q4 2017 Community Service Award to Russell Keith-Magee for his contributions to Django, for his work on the BeeWare project, and for being an active international speaker at PyCons.

Russell’s adventures with Django

Russell has been a core developer on the Django project since January 2006. Additionally, Russell has been a mentor in the Google Summer of Code for both the Django and BeeWare Projects since 2008.

Russell became a professional Python programmer just when the concept of web frameworks was emerging. He explains, “coming from a desktop UI background, I didn’t understand the fundamental shift that web programming required, or how these frameworks mapped onto those requirements”. When Russell discovered Django, however, this technology just clicked. Within a short period of time he had conjured up a working website. “But more importantly, Django allowed me to understand why the web worked the way it does”.

These were the early days of Django development and Russell rolled up the sleeves to start helping the nascent project. At first he, “dug into a couple of small issues, then some bigger ones - and before long, I’d been offered commit access.”

BeeWare: The IDEs of Python

Russell is also the founder of the BeeWare Project - a project developing tools and libraries for cross-platform native user interfaces in Python. One of the key contributions of this work is expanding the availability of Python onto mobile and browser platforms.

In his quest to build a rich, graphical debugger for Python, Russell found he needed a cross-platform, Python-enabled widget toolkit. It was then that he had a stroke of inspiration, “Why not have one code base but multiple apps?” The idea was to, “support Python natively on iOS and Android, and, at the same time, build a cross-platform UI toolkit that was Python-native.”

Five years into the BeeWare Project, Russell, and his fellow BeeWare apiarists were focusing on getting the BeeWare tools to the point where they would be a viable option for user interface development.

BeeWare is now a “spare time” project for Russell. He wishes to work on it full time and, so is looking for means ways of financial support. “It’s difficult to make a business case for something that is (a) Open Source, and (b) not yet ready for commercial usage.” In his words, “this highlights two existential threats for Python.”

The first of these threats is the growth of mobile and browser development . This “will have a profound impact on the viability of Python as a language.” He rejects the claim that JavaScript is a better language , but admits it has a key advantage: “it’s available in the browser, the most important new platform of the last 20 years”. Russell recommends that “Python should focus more on finding ways to target these new and emerging platforms and plan for where our industry is moving”.

The second threat to Python is the threat he sees to , the Python ecosystem - and the broader Open Source ecosystem. Open Source supports the existence of thousands of companies but the development and maintenance of the Python and other open source tools, critical to their existence, is massively* underfunded. For instance, PyPI is a classic example of this second sort of problem: it has active commercial usage but limited support from commercial users. This threat will continue to exist in the “absence of ongoing source of funding”. 

Russell’s Advice for Beginner Pythonistas

Russell’s numerous contributions to the Python community reflect his core belief in service to the bigger project. For beginning Pythonistas, Russell advices to give back to the community.

“As someone coming into the community, you may not think you have a lot to offer, but you do “.

He thinks there are many “activities around the language like user groups, meetups and conferences, that need people to help organize.” These are as essential as coding, for the development of a language, language community. So no specific skill is required to jump in, so come one, come all. 

Dr. Russell Keith-Magee, DjangoCon 2017

These words are an inspiration to us all no matter if we’re beginners or experienced Pythonistas. In short, thank you Russell for your years of service and contributions to the Python community and for those yet to come.