Re: Patch: Update RuleDispatch for python-2.7

On Mon, Aug 02, 2010 at 04:59:18PM -0400, P.J. Eby wrote:
> At 02:35 PM 8/2/2010 -0400, Toshio Kuratomi wrote:
> >The maintainers took a look but spotted a non-technical change right off the
> >bat that isn't necessarily a deal-breaker but does mean a huge amount of
> >work and potentially could cause problems.
> >
> >Looks like 0.5.2 relicensed to the Apache Software license v2.  That license
> >is incompatible with the GPLv2
> 
> Ah, fudge.  I could've sworn it was GPL-compatible.  It's just this
> sort of licensing issue I was trying to avoid.
> 
> That *really* sucks, as I rather prefer Apache.  Oh well.
> 
> >Would you be willing to change the license back to PSF or ZPL (with
> >versions if possible)?
> 
> How about just ZPL 2.1?  I'd really like to drop the alternate
> methods of licensing stuff.
> 
That would be great!  My handy-dandy license page says that ZPL-2.1 would be
compatible with GPLv2 and GPLv3 so that works out fine.

> By the way, I just got done making a BytecodeAssembler 0.6 release
> that has full 2.7 support (no test failures, full forward/back
> emulation), and I've updated PEAK-Rules in SVN to eliminate all the
> spurious doctest failures.  (At least, I can't get any more such
> failures across 2 machines and 5 versions of Python.)

Excellent!  pypi seems to be down right now but I'll grab the new release as
soon as I can.  Did you license 0.6 as ZPL-2.1 by any chance?  Or is it
still Apache License?

-Toshio

_______________________________________________
PEAK mailing list
[email protected]
http://www.eby-sarna.com/mailman/listinfo/peak

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAkxXeKEACgkQX6yAic2E7kjlDACgg/zI3O0NOfvzMWkyYBxjisaW
pmYAnA+AB0pIVzPDOGmGfqIMZh6MQtNI
=qi4m
-----END PGP SIGNATURE-----