Monday, April 16, 2018

Support the PSF during the 2018 Fundraising Drive

The PSF is launching an exciting fundraising drive with a goal of raising $20,000.00 USD by May 12th.  The drive begins April 16, 2018 and concludes at PyCon on May 12th.

Your donations help the Python community worldwide by supporting sprints, meetups, community events and projects, the Python Ambassador Program, fiscal sponsorships, and of course, software development and open source projects. All of these initiatives help improve the Python community and Python tools that you use daily. The work cannot be done without the generous financial support that individuals and organizations provide us.

It is easy to donate - simply click on the amount you would like to give, and enter your email address. Confirm your contribution and you will be able to pay with your PayPal account or a credit or debit card. Contributions are tax deductible for individuals and organizations in the United States.

To thank you for your financial support, we will enter you in a drawing to win the following prizes:

  • Ticket to PyCon 2019 (1 winner)
  • Photos with Guido van Rossum at PyCon 2018 (must be present to win)
  • Lunch with Guido van Rossum at PyCon 2018 (8 winners, must be present to win)
  • Custom designed Guido T-Shirt (5 winners)
  • “I Donated” stickers
  • Custom designed “Guido” stickers

More details on contributing can be found on the 2018 Q2 Fundraising Drive page. No donation is necessary to enter the drawing.

We at the PSF want to thank you for all that you do. Your support is what makes the PSF possible and is greatly appreciated by the Python community.

Also, if you would like to share the news about the PSF’s Fundraising drive, please share a tweet via these tweet buttons or copying the text in the following:


  • Our Q2 2018 Fundraising Drive starts April 16, and concludes at @PyCon on Saturday, May 12. Help us raise $20K! https://www.python.org/psf/donations/2018-q2-drive/ #idonatedtothepsf


  • Contribute to our fundraiser & help us reach our goal of $20K. The PSF is a non-profit organization entirely supported by its sponsors, members, and the public. https://www.python.org/psf/donations/2018-q2-drive/ #idonatedtothepsf



Thursday, April 12, 2018

Python Software Foundation Fellow Members for Q1 2018


We are happy to announce our 2018 1st Quarter Python Software Foundation Fellow Members:

Amber Brown

Ernest W. Durbin III

Eyitemi Egbejule

Michael Kennedy

Nathaniel Smith


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 frameworks, maintaining critical Python infrastructure, organizing Python events, hosting Python podcasts, 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 python.org. Here is the nomination review schedule for 2018:

  • Q2: April to the end of June (01/04 - 30/06) Cut-off for quarter two will be May 20. New fellows will be announced before June 30. 
  • 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 still 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 python.org.

Thursday, March 29, 2018

Python Developers Survey 2017 Results: Learn about the community

At the end of 2017, the Python Software Foundation, together with JetBrains, conducted an official Python Developers Survey. We set out to identify the latest trends and gather insight into how the Python development world looks today. Over 9,500 developers from almost 150 countries participated to help us map out an accurate landscape of the Python community. We are super excited to share the results of the survey with you!


We hope the survey findings will help us better understand the current state of the Python developer community and answer some potential questions. Included in the survey results is information about the most popular types of Python development, trending frameworks, libraries and tools, additional languages used together with Python, adoption rates of different Python versions, and gain many other insights into the world of Python.

We couldn’t include all the potential findings in the report. Therefore If you have specific unanswered questions please send them to us and we’ll dig into the data for an answer. Or if you want to delve into the data yourself, we’re also sharing the raw survey data, which anyone can use to arrive at their own conclusions and generate additional findings.

If you do go the extra step and dive into the survey data, we’d be interested to learn about your findings! Please share them on Twitter or on other social media by tagging @jetbrains‏ and @ThePSF with the hashtag #pythondevsurvey2017. We’re also open to any suggestions and feedback related to the survey so we can run an even better one next time.

Huge thanks to all the participants of the survey and to the amazing team at PSF and JetBrains that worked hard to make this happen!

Monday, March 26, 2018

Warehouse: All New PyPI is now in beta


  1. Context
  2. Migrating
    1. New PyPI Features
    2. Deprecations
  3. Future Plans
  4. Security
  5. Please test!
    1. Workflows
  6. IRC/Twitter livechat hours
  7. Contact us

The all new Python Package Index is now in beta at pypi.org. We predict the full switch will happen in April 2018 (roadmap), so here's a heads-up about why we're switching, what's changed, and what to expect. To get an email when the new site replaces the old one, please sign up for the low-traffic PyPI announcements email list.

    Context


    The legacy PyPI site at pypi.python.org started in the early 2000s, before modern web frameworks. The legacy codebase has made it hard to maintain and even harder to develop new features, even as past maintainers put in tremendous effort to continuously reduce outages.

    The new PyPI at pypi.org (codebase: Warehouse) looks more modern, and is up-to-date under the hood too. A modern web framework (Pyramid), 100% backend test coverage, and a Docker-based development environment make it easier for current and new developers to maintain and run it and add features.

    Thanks to Mozilla's Open Source Support funding, we have designed and added new features, overhauled infrastructure, and worked towards redirecting traffic to the new site and shutting down the old one. The full switch will include redirecting browser and pip install traffic from the old site; then, sometime in late April or early May, the legacy site will be entirely shut down.


    Migrating


    You may not need to change anything right away. Thanks to redirects, your sites, services, and tools will probably be able to seamlessly switch to the new site.

    Users: On Windows and Linux, no change is necessary as long as your version of OpenSSL supports TLSv1.2. pip install should work as normal. macOS/OS X users running version 10.12 or older need to upgrade to the latest pip (9.0.3) to connect to PyPI securely:


        curl https://bootstrap.pypa.io/get-pip.py | python

    Package maintainers: If you use setup.py upload to upload releases, we recommend you switch to Twine. New PyPI takes the same username/password as legacy PyPI did. If you have problems, follow the packagers' migration guide.

    API users: follow the API users' migration guide.

    If you're affected by a deprecation (below), you should adapt and migrate by early April 2018. For help, come to a livechat or contact us. Sign up for the low-traffic PyPI announcements email listto get a heads-up when we have a more precise date.


    New PyPI Features

    • mobile-responsive UI  
    • chronological release history for each project (example)  
    • easy-to-read project activity journal for project maintainers  
    • better search and filtering  
    • support for multiple project URLs (e.g., for a homepage and a repo)  
    • support for Markdown READMEs for source distributions (soon: wheels too)  
    • user-visible Gravatars and email addresses for maintainers  
    • no need to "register" a project before initial upload  
    • better accessibility (and more work to come)  
    • newer backend infrastructure, supporting new features and a more scalable PyPI  


    Deprecations


    Things that already have gone away (sometimes for policy or spam-fighting reasons) include:

    Things that will go away once legacy PyPI shuts down:

    Late 2018 or later:


    Future plans


    See our issue tracker. Includes:

    For updates, please sign up for the low-traffic PyPI announcements email list.

    Security


    If you find any potential security vulnerabilities, please follow our published security policy. Please don't report security issues in Warehouse via GitHub, IRC, or mailing lists. Instead, please directly email the security team.


    Please test!


    The point of the beta is to find and fix bugs. Please help us. Most of these workflows you can test on pypi.org, using the same login as you use on pypi.python.org (legacy PyPI). For testing destructive actions, like removing an owner, deleting a project, or deleting a release, please use test.pypi.org.


    Workflows


    Package users:
    • Register/confirm a new user  
    • Login/logout  
    • Reset password  
    • Search for projects  
    • pip install a package  
    • Download release files via browser  
    • Call JSON, RSS, Simple, and XML-RPC APIs  

    Project maintainers:
    • Add/remove a maintainer  
    • Add/remove an owner  
    • Transition ownership  
    • Remove a project  
    • Remove a release  
    • View journals for a project  
    • View journals for a release  
    • Upload a new release (source distribution and wheel; upgrade your versions of twine and setuptools first)  
    • Confirm display of project description, release history, download files, project links, maintainers, tags, and classifiers (example)  


    IRC/Twitter livechat hours


    Warehouse developers will be in IRC, in #pypa-dev on Freenode, and on Twitter (#newpypi), available to talk about problems you run into, or about how to hack on Warehouse:
    1. Tuesday, March 27th, 9am-10am PDT, noon-1pm EDT, 18:00-19:00 CEST, 9:30pm-10:30pm India, 16:00-17:00 UTC  
    2. Friday, March 30th, 10-11am EDT, 16:00-17:00 CEST, 7:30pm-8:30pm India, 14:00-15:00 UTC  
    3. Tuesday, April 3rd, 8am-9am PDT, 11am-noon EDT, 17:00-18:00 CEST, 8:30pm-9:30pm India, 15:00-16:00 UTC  
    4. Thursday, April 5th, 5pm-6pm PDT, 8pm-9pm EDT, (April 5th) 8am-9am Manila, (April 5th) 10am-11am Melbourne, (April 5th) 0:00-1:00 UTC  

    Feel free to drop in! (By participating, you agree to abide by the PyPA Code of Conduct.)


    Contact us



    (By participating, you agree to abide by the PyPA Code of Conduct.)

    Thank you for using PyPI!

    Tobacco Warehouse in Louisville, Kentucky 1906

    Monday, February 26, 2018

    Python package maintainers, help test the new PyPI!


    Warehouse is a next-generation Python Package Repository which will replace the existing code base that currently powers PyPI. (See the source code on GitHub, and roadmap for details.) We are seeking maintainers of projects on PyPI to test it and send us bug reports, and we're seeking new contributors to Warehouse.

    Since Warehouse must be a reimplementation of the existing PyPI, please focus initially on any differences, missing features, or incorrect behavior that is exhibited on pypi.org that affect your workflows for account management and package maintainership. We'll be soliciting feedback on other concerns soon! Feedback on user experience, accessibility, and overall ease of use are welcome. Go to the pre-production deployment at pypi.org and try it out!

    Background


    Last year, the PSF's Packaging Working Group successfully applied for a grant from Mozilla's Open Source Support program. Mozilla awarded USD 170,000 to get PyPI upgraded. The team's been working since early December—see our progress reports and roadmap—and pypi.org now has the essential features that package maintainers, and most other users, need.


    Guidelines for Particpation


    By participating, you agree to abide by the PyPA Code of Conduct.
    You should sign up for the PyPI Announcement Mailing List for updates.

    Things to test


    Most of these you can test on pypi.org, using the same login as you use on pypi.python.org (legacy PyPI). For testing destructive actions, like removing an owner, deleting a project, or deleting a release, please use test.pypi.org, which has an entirely separate package index.

    Workflows


    • Add/Remove Maintainer
    • Add/Remove Owner
    • Transition Ownership
    • User Registration and Confirmation
    • Login/Logout
    • Password Reset
    • Remove a project
    • Remove a release
    • View Journals for a Project
    • View Journals for a Release
    Warehouse has handled new projects and new release uploads since last summer, so those workflows are not the most important to test now. The list of workflows above are the ones we request you to exercise.

    Security


    If you find any potential security vulnerabilities, please follow our published security policy. Please don't report security issues in Warehouse via GitHub, IRC, or mailing lists. Instead, please directly email one or more of our maintainers.

    IRC livechat hours


    Warehouse developers will be in IRC, in #pypa-dev on Freenode, and available to talk about problems you run into, or about how to hack on Warehouse:
    1. Tuesday Feb 27th: 1700 UTC / noon-1pm EST
    2. Tuesday Feb 27th: 2300 UTC / 6pm-7pm EST
    3. Thursday March 1st: 1700 UTC / noon-1pm EST
    4. Thursday March 1st: 2300 UTC / 6pm-7pm EST
    Feel free to drop in!

    Notice


    We're working hard on nearly every aspect of the Warehouse codebase to get it ready for production deployment and we are shipping features nearly every day, so check back and maybe even try using pypi.org for your maintainer activities full time. Due to the rate of change some errors, downtime, and outright broken features may occur. We have some automated reporting of the scenarios in place, but let us know!

    Reminder: Sign up for the PyPI Announcement Mailing List to be kept in the loop as we continue this process.

    Dive into the code


    We've improved Warehouse's developer experience substantially in the last few months. We have several open "good first contribution" issues and a guide to getting started. One of our maintainers, Ernest W. Durbin III, wants to help you dive in and to give you Warehouse stickers, and has 30-minute 1:1 slots available to mentor you. We'll also be running a sprint at PyCon North America in May!

    Contact us



    Thank you for testing Warehouse! You're helping us launch sooner and future users of PyPI will appreciate it.

    — The PyPI Team



    Photo © Mark Hunter

    Wednesday, January 31, 2018

    The Python Software Foundation is looking for bloggers!

    Interview prominent Pythonistas, connect with the community, expand your circle of friends and learn about events in the Python world!


    The Python Software Foundation (PSF) is looking to add bloggers for the PSF blog located at http://pyfound.blogspot.com/. As a PSF blogger you will work with the PSF Communication Officers to brainstorm blog content, communicate activities, and provide updates on content progression. Example of content includes PSF community service awardee profiles, details about global Python events and PSF grants, or recent goings-on within the PSF itself. One goal of the 2017 - 2018 PSF Board of Directors is to increase transparency around PSF activities by curating more frequent blog content.

    The Python Software Foundation is a 501(c)(3) non-profit corporation that holds the intellectual property rights behind the Python programming language. We also run the North American PyCon conference annually, support other Python conferences/workshops around the world, and fund Python related development with our grants program. To see more info on our grants program, please read: https://www.python.org/psf/grants/.


    Job Description

    • Capacity to contribute one to two blog posts per month
    • Passionate about Python and the global Python community
    • Independently report progress and activities to Python Software Foundation Staff and Communication Officers on a monthly basis
    • Actively brainstorm content ideas for blog content individually as well as with Python Software Foundation Staff and Communication Officers

    Needed Experience

    • Ability to work independently and on virtual teams
    • Familiarity with Python programming
    • Experience contributing to a technical blog or website in English
    • Professional proficiency in English

    Bloggers for the Python Software Foundation receive a fixed fee per post they write.

    To apply please email two to three examples of recent articles (e.g. personal blog, contribution to professional publication) written in English as well as a brief description of your writing experience to psf-blog-apply@python.org. Please include in the email subject "PSF Blogger Application - (Your Name)". If you have questions, direct them to psf-blog-apply@python.org as well. The Python Software Foundation will be accepting applications until 11:59:59pm Pacific Standard Time Thursday, March 1, 2018.

    Monday, January 08, 2018

    2017: A year in review

    In 2017, Python was both the most popular and the fastest-growing programming language. At least, we can plausibly claim that, based on statistics recently published on the Stack Overflow blog. As David Robinson writes:
    Python is an unusual case for being both one of the most visited tags on Stack Overflow and one of the fastest-growing ones. (Incidentally, it is also accelerating! Its year-over-year growth has become faster each year since 2013).
    Python's versatility, clean syntax, and welcoming community have continued to win people over, and now we have a new advantage: data science is a growth industry and Python is positioned ideally. Who would have thought our 26-year-old language would outrun Javascript, Go, and Swift? Python's rapid growth in 2017, and its bright prospects for 2018, are the community's greatest achievement of the year.

    This past year the Python Software Foundation continued to give out grants and support many events all around the world. There are too many events to list in this post, but you can see some of the resolutions we passed in our monthly minutes. Through our awards program, we recognized members within our community for their work and tireless efforts. We made changes to our bylaws to make the PSF more sustainable. Additionally, the PSF board members met in person twice this year to have important discussions about our future goals and direction. We created a process for accepting new Fellow members. Lastly, Mozilla granted the PSF's Packaging Work Group a grant to work on the future PyPI, Warehouse.

    Grants

    In 2017, the PSF awarded over 220 grants (40 more than last year) amounting to more than $257,000. Prior to 2017, most grants were reviewed by the Board of Directors. Of the $257,000 approximately 25% of the funds went to requests from Africa, 23% went to Europe, 19% went to Asia, 18% went to North America, 13% went to South America, and 2% went to Australia. In July of this year we transitioned all grant requests to our Grant Work Group. This operational improvement has freed up our Directors to have more discussion about the PSF's direction and future goals. The PSF is grateful for the Grant Work Group volunteers for all of the work they do reviewing requests.
    The Python community had several first time conferences in 2017. Here are a few:

    PyCon Pune
    PyCon Pune was a successful conference. The conference held the first set of Python development sprints in India. The conference had around 550 attendees and a single track. Even though they are unable to host one in 2018, we hope to see one in 2019! Check them out on Twitter!


    Conference t-shirt for PyCon Pune 2017: "“Came for the language, stayed for the community”, by Brett Cannon"


    North Bay Python

    North Bay Python 2017 was in December in Petaluma, California. They had an amazing turn out of new comers. "Roughly 40% of the 230 attendees" were first time tech-conference attendees says Christy Heaton. You can read more about the conference here. Follow their Twitter for future updates.


    PyCon Pakistan
    PyCon Pakistan happened in December of 2017 at the FAST University Lahore venue. They had close to 500 attendees, which is a great turn out for a first time conference. Follow them on Twitter for updates on a possible PyCon Pakistan 2018.

    Awards


    Distinguished Service Award

    Building on the ideals of the Foundation's Community Service Award, the Distinguished Service Award is an offer of recognition for exemplary contributions to the Python community. The Foundation's highest award is given for actions which carry significant impact that shapes the Python world, whether through contributions of code, efforts in community action, or otherwise.

    We do not award the DSA often, but when we do, we give it out to invaluable, long-time community contributors. In 2017, we voted to award the DSA to Tim Peters.

    Alex Martelli nominated Tim a few years back saying,
    His technical contributions to Python have been absolutely immense: even just for "timsort" he'd deserve the award, and he's done SO much more than just that, even just on the technical plane! In addition to his enormous number of technical contributions (let's not forget doctest, timeit, etc, etc...!!!), for years, he was the friendliest, funniest, most helpful and technically deep contributor to the Python mailing list; his chapter intro in the Python Cookbook is an absolute gem; and he's ALSO striven to help organizationally. I think he's an outstanding candidate.
    It's true that most of his contributions were a while ago, but this award is not about "what have you done for me lately"; it's a "lifetime-achievement" award, and, this being the case, nobody deserves it more than Tim.


    Community Service Awards

    This year we awarded Community Service Awards to six contributors. Eric Floehr received an award for his involvement and chairing of PyOhio Conference. We recognized Thomas Kluyver for his contributions to the Scientific Python Community.  Lynn Root also received a community service award for her work as the founder of the San Francisco Chapter of PyLadies, as a member of the Django Software Foundation, and as a tireless volunteer at PyCon. Glyph Lefkowitz was recognized for his work on the Twisted network programming framework. Brian Costlow received an award for his work organizing and chairing PyOhio, and for being the head volunteer for PyCon US captioning. Ian Cordasco received a community service award for being the PSF elections administrator and for mentoring women in the Python community.  We will announce two more awards for Q4 at the end of January.


    Frank Willison Memorial Award

    Every year the Python Software Foundation awards the Frank Willison Memorial Award to a member(s) of the Python community. The purpose of this award is to recognize the outstanding contributions that Python community members have made having began as an award, “established in memory of Frank Willison, a Python enthusiast and O'Reilly editor-in-chief, who died in July 2001”.

    The Python Software Foundation award the 2017 Frank Willison Award to Katie Cunningham and Barbara Shaurette in recognition of their continuing work to create and run their Young Coders classes, along with freely distributing their teaching materials. Read more about their story in our post from May 2017.
    Barbara Shaurette receiving her award. Unfortunately, Katie Cunningham could not attend to receive her award in person.


    Bylaw changes

    During our yearly elections, we made several changes to our bylaws in 2017. We eased the requirement for members needing to certify yearly if they wanted to vote on Foundation matters. Additionally, we instituted a bylaw that would allow a work group to approve new PSF Fellow members. We created staggered board terms so our work is more sustainable and so we have more continuity. We established two Direct Officer positions in an effort to become a more stable and mature board. Lastly, we also updated the way compensation is regulated so the entire board has control of it instead of the President. To read more details about the changes, please check out our post from July 2017.


    Launch of PSF Fellow Work Group

    We are happy to report that we now have a way to accept new PSF Fellow Members. With the opening of membership back in 2014, we overlooked a way to accept new Fellow level members so that has been on hold until now. We've announced two rounds of Fellow Members since we launched:

    If you are interested in nominating someone, check out the info page.


    MOSS Grant to deploy Warehouse

    Python programmers wondered for all of 2017, "When will the new PyPI be done?" In November we announced a breakthrough: Mozilla granted $170,000 to complete PyPI's rewrite and make it the official package index.

    We finished the year strong by starting work on Warehouse (the improved PyPI) via the grant awarded by Mozilla, through the Foundational Technology track of their Open Source Support Program. The PSF's Packaging Work Group is in full swing for the next six months working on various bug fixes, improvements, and implementations. If you are interested in more details, please see the grant announcement.