Shrinky-dink Python (also, non-Unicode Python build is broken)

Larry Hastings larry at
Tue Jan 17 18:39:06 EST 2006

> Are you willing to monitor and fix new Py_USING_UNICODE issues or
> are you proposing just to produce a patch now and then expect
> contributors to maintain this feature?

Neither, I suppose, or perhaps both.  I am proposing to produce a patch
now which fixes the non-Unicode build under Windows.  However, I don't
expect anything out of other contributors, and I don't set Python
contribution policy.  (Obviously the stewards of the Python tree don't
care whether contributions break the non-Unicode build.  But that's a
fine policy; after all, they've already got enough to do, and in any
case I'm the first person to even notice.)  If this patch is accepted,
and some future contribution breaks the non-Unicode build again, and I
discover the breakage, I might very well create a second patch to
re-fix it.

Since I'm seemingly the only person who cares about non-Unicode builds
on Windows, I suggest this approach would work just fine.


More information about the Python-list mailing list