On Tue, Jan 16, 2001 at 08:39:35PM -0500, Guido van Rossum wrote:
>I expect that there will be an alpha2, but I still recommend that you
>check in *something* that works for alpha1, to get maximal testing
>coverage. Alpha1 may slip a day or so (Jeremy and I are both late
>with our big patches, respectively nested scopes and rich comparisons,
>that we really want to have in alpha1).
OK; thanks for the pronouncement!
I've checked in all the smaller changes that shouldn't break anything.
All that's left now is to actually enable the new feature, which
requires the nasty changes:
* In the top-level Makefile.in, the "sharedmods" target simply
runs "./python setup.py build", and "sharedinstall" runs
"./python setup.py install". The "clobber" target also deletes
the build/ subdirectory where Distutils puts its output.
* Rip stuff out of the Setup files. Modules/Setup.config.in only
contains entries for the gc and thread modules; the readline,
curses, and db modules are removed because it's now setup.py's
job to handle them.
* Modules/Setup.dist now contains entries for only 3 modules --
_sre, posix, and strop.
Guido and Jeremy are rushing to finish their patches in time for the
alpha release, though Guido seems to be checking in the rich
comparison stuff now. I don't want to impede them by making them stop
to debug build problems, so I can either wait until they've landed
their changes (at which point there's nothing major left, I think), or
they can simply not do a 'cvs update' after the serious changes go in.
Thoughts?
--amk
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