[Python-Dev] frozen exceptions.py (was: win32 specific exception in the core?)

[Greg Stein]

On Tue, 8 Feb 2000, Fredrik Lundh wrote:
> Barry A. Warsaw wrote:
> > Absolutely.  If string-based standard exceptions are removed for 1.6,
> > we need a fool-proof way of getting exceptions.py.  Remember, my first
> > attempt at this stuff made that Python code a BACS[*] that got
> > exec'd.  I'm sure there are better ways of doing that now, and I think
> > exceptions.py has settled down enough to warrant cooling it for 1.6.
> 
> let's just make it a built-in module.  I have a 95% complete
> "exceptions.c" implementation somewhere.  I'll take a look.
> 
> (for more info, cc effbot@telia.com.  GvR won't
> add the effbot to this list before SRE is finished ;-)

Why C? Implement it in Python and freeze the sucker. We all know that
Python is much more maintainable. With a few simple changes, we can also
make this freeze process very straight-forward and part of the standard
build process.

There are quite a few things that could be done in Python, then just
frozen into the binary. Just wait until I start arguing for the parser and
compiler to be written in Python, frozen in, and we dump their C
equivalents... :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/