Skip to main content

For Microsoft, Python support extends far beyond Windows installers

You might have known that Python's 1.0 release came at the start of 1994, but did you know Microsoft shipped its Merchant Server 1.0 product built on Python only a few years later in 1996? Microsoft, this year's Keystone sponsor, has long been a user and supporter of Python, with a history of use within build and test infrastructure and individual users all around the company. There are even a few lawyers writing Python code.

In 2006 they introduced the world to IronPython, a .NET runtime for Python, and later the excellent Python Tools for Visual Studio plug-in in 2011. They continue to release Python code, as it's "a must-have language for any team that releases developer kits or libraries, especially for services on Azure that can be used from any operating system," according to Steve Dower, a developer on Microsoft's Python Tools team.

"Python has very strong cross-platform support, which is absolutely critical these days," says Steve. "It’s very attractive for our users to literally be able to 'write once-run anywhere.'

"The breadth of the community is also very attractive, especially the support for scientific use," he continued. Microsoft has been a significant donor to the Jupyter project (formerly IPython) as well as a platinum sponsor of the NumFOCUS Foundation.

Along with supporting those projects, they have also been providing MSDN subscriptions to the core Python team to assist with development and testing on Windows. Beyond supporting the existing developers, they've jumped in the ring themselves as one of the few companies to employ developers working on CPython itself. "Python has done an amazing job of working well on Windows, and we hope that by taking an active involvement we can push things along further," offers Steve, whose work includes being a core developer on the CPython project.


Steve's CPython work has focused around Windows issues, including an improved installer for 3.5. Additionally, the team was able to come up with a special package for Python users: Microsoft Visual C++ Compiler for Python 2.7. Due to Python 2.7 being built on the Visual C++ 2008 runtime, which is no longer supported, they created this package to provide the necessary tools and headers to continue building extension modules for Python 2.7, which will live through at least 2020 as was announced at last year's language summit.


Along with efforts on Python itself, they're hard at work on improving tooling for the upcoming Visual Studio 2015 and Python 3.5 releases. "Practically everything we do will integrate with Visual Studio in some way," says Steve of Python Tools for Visual Studio. "PTVS has been free and open-source from day one, and combined with Visual Studio Community Edition makes for a powerful, free multi-lingual IDE."

As for what's next with PTVS, Steve says, "we try and be responsive to the needs of our users, and we are an open-source project that accepts contributions, so there’s always a chance that the next amazing feature won’t even come from our team. We've also recently joined forces with the Azure Machine Learning team and are looking forward to adding more data science tooling as well.

"We want new and experienced developers alike to have the best tools, the best libraries, the best debugging and the best services without having to give up Linux support, Visual Studio, CPython, git, or whatever tools they’ve already integrated into their workflow."

When it comes to PyCon, they see it as "a learning opportunity for Microsoft, as well as a chance for us to show off some of the work we’ve been doing." "For those of us at Microsoft who always knew how great the Python community is, it’s also been great to bring our colleagues and show them.

"We love that PyCon is about building and diversifying the community, and not about sales, marketing and business deals," says Steve. If you head to their booth in the expo hall, you'll find out first hand that they're there to talk about code and building great things. They're looking forward to showing off some great new demos and have exciting new things to talk about.

The PyCon organizers thank Microsoft for another year of sponsorship and look forward to another great conference!

Comments

Popular posts from this blog

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…