|
On Sun, 27 Feb 2005, Carey Evans wrote:
Not really, I think you've covered it. I tend to agree that we'd be best to create a Python + GLib branch from HEAD for anyone that's interested in the future, then move development from b0-16 to HEAD according to what people are actually working on.
There's a lot that can be done with just the standard C library, with autoconf to discover differences between platforms.
As far as future development goes, I believe we'd get more done without trying to do parallel development of stable and unstable. Make and test the changes, then announce a stable release once it works well.
James Rich
It's not the software that's free; it's you. - billyskank on Groklaw
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.