On 09/10/2012 12:49 PM, Mark Lawrence wrote: > My offer to test on Windows still holds. The question is test what? > Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then > different versions of Visual Studio are needed as detailed here > http://bugs.python.org/issue13210. I can't see much sense in me trying > to build and test all that lot while other volunteers are doing exactly > the same thing at the same time. Is there a cunning plan somewhere to > cover this that I've missed? >
The process is usually that the release is tagged in github, a tarball is created, and then various platform specialists create the binary releases. For the last release Christoph Gohlke did the Windows builds, and I assume he is able to do that again this time. Perhaps it makes sense to coordinate with him to share some of that work? Anything we can do to lessen the burden on any one person is always appreciated. Even leading up to the tagging of the release candidate, it's always helpful to build from github periodically and test on the platform and version of Python that's most important to you, and report back into the issue tracker any test failures or other glitches. Mike ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
