> I'm wondering if there is any interest in me making regular, > basically untested win32all builds against the current Python CVS > tree? > > It would be fairly simple for me to do - I run against CVS Python, > so it is really just bundling up my latest built files into an > installer .EXE. I would only do it for the current CVS trunk - ie, > no Python 2.2 or earlier builds in this form. However, I would only > bother if there were people willing to use it. I figure that if > there aren't people in this forum who would use it, I won't find > them anywhere ;) I think that would be useful, especially if the current 2.2-compatible win32all does not work with 2.3, or if you have added features since that was last released. > OTOH, people in this forum using CVS Python on Windows may prefer to > use CVS and build their own win32all - I really have no clue ;) Not me. I know how to build and install Python from source on Windows, but setting up another project is a major pain for a Unix weenie like me, so I'd much prefer a binary distribution. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4