Brian,

Thanks again for helping here!

Two additional experience stories on why MSDN is valuable for those of working on the Python language:

Some of us otherwise don't run Windows devices, but would like to support Windows, across potentially a range of versions and natural languages — and their encodings. In particular, we have used MSDN to ensure that Jython runs quite reasonably well on Windows. (This was a big focus in the Jython 2.7.0 release in fact, and continues to be the case.)
I also used an Excel download from MSDN to verify that Jython code going against Apache POI (https://poi.apache.org/) worked correctly with both Windows and Excel; and therefore was able to write up this experience with Josh Juneau for an article in the Nov/Dec 2015 issue of Java Magazine.

- Jim

On Wed, Aug 15, 2018 at 9:18 AM, Steve Dower <steve.dower@python.org> wrote:

On 15Aug2018 0650, Brian Curtin wrote:

This will give you access to Microsoft's Developer Network, which includes access to things like Visual Studio and Windows licenses that we can use for working on Python.

Just to clarify one thing: you don't need a special license to get Visual Studio Community Edition to work on Python, even within a big company - it's free for open source work, and has everything we need.

But request the MSDN Subscription anyway. It looks good to have a lot of demand coming from the Python community :) (plus it should include a chunk of Azure time if you need VMs, and probably some VSTS bonuses these days though I haven't checked that).

Thanks for everyone's work on Python!

+1, and thanks Brian for continuing to coordinate this!

Cheers,
Steve
_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/