Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

motivation.rst add real problem to answer why #42

Open
wants to merge 2 commits into
base: source
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 17 additions & 7 deletions motivation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,23 @@
Why mingwpy?
############

Python.org distributes binary installers for Python that are built with
:term:`MSVS`.

It is possible to install a version of MSVS that will build Python extensions
written in C.

So |--| why do we need mingwpy?
Python extensions for Windows should be compiled with the version of
:term:`MSVS` that was used to compile Python itself. The problem is that for
every Python this version is different.

========== ======================
Python 2.7 Visual C++ 2008 (9.0)
---------- ----------------------
Python 3.3 Visual C++ 2010 (10.0)
---------- ----------------------
Python 3.4 Visual C++ 2010 (10.0)
---------- ----------------------
Python 3.5 Visual C++ 2015 (14.0)
========== ======================

So to build extension for 2.7, 3.4 and 3.5 you need to install 3
different compilers. For other Python versions see the full list at
http://matthew-brett.github.io/pydagogue/python_msvc.html

********************************************
MSVS can be painful to install and configure
Expand Down