On Thu, Jan 21, 2010 at 5:24 PM, Collin Winter <collinwin...@google.com> wrote: > On Thu, Jan 21, 2010 at 12:56 PM, Paul Moore <p.f.mo...@gmail.com> wrote: >> Windows compatibility is a big deal to me. And IMHO, it's a great >> strength of Python at the moment that it has solid Windows support. I >> would be strongly *against* this PEP if it was going to be Unix or >> Linux only. As it is, I have concerns that Windows could suffer from >> the common "none of the developers use Windows, but we do our best" >> problem. I'm hoping that having U-S integrated into the core will mean >> that there will be more Windows developers able to contribute and >> alleviate that problem. > > One of our contributors, James Abbatiello (cc'd), has done a bang-up > job of making Unladen Swallow work on Windows. My understanding from > his last update is that Unladen Swallow works well on Windows, but he > can comment further as to the precise state of Windows support and any > remaining challenges faced on that platform, if any.
Unladen Swallow currently works well on Windows, compiling with MSVC. The CPython regression test suite passes. It has been a while since I've run Unladen's collection of 3rd party tests but things looked good there as well. All the tests that were working under CPython on Windows were also working under Unladen. Some of the tests have Unix assumptions in them that cause them not to work on Windows. I've tried to get some of these fixed upstream but I haven't yet tried to get newer versions into the Unladen SVN repo. Keeping things working on Windows hasn't been that difficult. Most of the effort recently has been in simply updating the project files to include any new source files. Occasionally there will be a problem with LLVM due to tracking LLVM's trunk which may be broken on Windows at the time a new version is pulled in. As the plan is to work with released versions of LLVM after 2.7 I don't anticipate this being a problem in the future. I'm using Visual Studio Express which doesn't have the ability to compile PGO or x86-64 binaries so those are untested. I've tried to keep the project files correct for those targets so hopefully it shouldn't be too much work for somebody with the full version of Visual Studio to get them working. The project files probably need a bit of other work. Currently LLVM has to be built in a separate step before Unladen Swallow can be compiled. It would be nice to automate this and properly track dependencies but I have not attempted to do this. I'd be happy to work with someone who has experience with the CPython project files to get this into shape. Overall I don't think that merging Unladen Swallow will unduly increase the burden of Windows support. Most of the code that has been added is fairly platform independent. Any Windows-specific complications with, for example, execution of generated machine code are handled by LLVM and are invisible at this level. -- James Abbatiello _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
