Ok, I'll look at doing that. I'm sure that I could wrangle CCP into making such a machine available, btw, but that depends on what we mean by _available_. Something outside the firewall with a remote desktop is conceivable. Meanwhile, I'll see how much of a chore this is. K
-----Original Message----- From: Richard Tew [mailto:[email protected]] Sent: 2. febrúar 2013 00:03 To: Kristján Valur Jónsson; The Stackless Python Mailing List Subject: Re: [Stackless] Python 3.3 On Sat, Feb 2, 2013 at 8:47 AM, Kristján Valur Jónsson <[email protected]> wrote: > Oh, that is long done :-) > If you had read the last few posts you would have noticed. > What is now needed is to generatw binaries and such from the branches > in the repository. > We also need to create the 3.4 branct but that's a different (and all > together more tedious) story. If we had access to a Windows build machine with a purchased Visual Studio license available, ideally we could build these automatically. For the most part we could do this with the exact same process which mainline Python uses. Ideally, we'd run the standard unit tests, the Stackless unit tests, and the standard unit tests with monkeypatching in place. I'd offer to build the installers, but I only have Visual Studio Express and it lacks the ability to build an installer. Here's my current installer building script: http://pastebin.com/rPCPKsjn Cheers, Richard. _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
