I'm with Martin. In these days of distributed version control systems, I would think that the effort for the Haiku folks to maintain a branch of Python in their own version control would be minimal. It is likely that for each new Python version that comes out, initially it is broken on Haiku, and then they have to go in and fix it. Doing that in their own version control has the advantage that they don't have to worry about not breaking support for any other minority operating systems, so I expect that all in all the cost will be less for them than if they have to submit these patches to core Python; and since that will definitely be less work for core Python, I would call that a win-win solution.
On Wed, Jan 14, 2009 at 2:31 PM, <s...@pobox.com> wrote: > > Raymond> The theory is that we don't want to support minority operation > Raymond> systems. My view is that we should support those systems to > Raymond> the extent that someone like the OP is willing to maintain the > Raymond> handful of deltas needed to get all tests to pass (the OP's > Raymond> comments indicate that very few customizations are necessary). > > +1. I would argue that Haiku OS is probably no more of a minority platform > at this point than OS2/EMX, which continues to be supported, at least at the > level if patches being applied to the source. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ 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