Matt Hickford added the comment: It matters if you're trying to write a library that builds reliably
1. On Linux 2. On Windows compiler=msvc 3. On Windows compiler=mingw32 (many people set this in distutils.cfg [1]) ...for all Python versions 2.6 through 3.5 (24 combinations!) Anyway I think I've got everything working simultaneously now. Thanks for your help. Yes I saw that blog post—your blog post—about compiler independence [2] from msvc 14.0 on. That's great news. Let me go study it. [1] http://stackoverflow.com/q/3297254/284795 [2] http://stevedower.id.au/blog/building-for-python-3-5-part-two/ On 29 September 2015 at 14:05, Steve Dower <rep...@bugs.python.org> wrote: > > Steve Dower added the comment: > > Well __version is determined by looking at sys.version to see what version > was used to build Python, so you aren't really getting the "actual" one, > though in practice it doesn't matter. > > For Python 3.5 and later you could get different versions from the one > that was used to build, but it will always be at least 14.0 and there's > deliberately no way for people to depend on that information other than in > C source code. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue25250> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25250> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
