Re: PEAK-Rules for Python3

I reached a point where multi dispatch worked. But sadly when PEAK-Rules =
needs to generate bytecode (predicate dispatch), things go awry.

As I see it, syntactic changes between python2 and python3 are small =
enough to have a code base working with both. But bytecode generation, =
needed to circumvent some python limitations, leads to another level of =
issues I do not completely understand.

As of licensing, it seems PEAK is licensed under PSF or ZPL.

=E2=80=94
Herv=C3=A9

> Le 17 mars 2015 =C3=A0 15:18, Cara <[email protected]> =
a =C3=A9crit :
>=20
> Oh, I see, the link in the list archives inappropriately included the
> period at the end of the sentence.  How far did you get?  What license
> is your code available under?
>=20
> Cara
>=20
>=20
> _______________________________________________
> PEAK mailing list
> [email protected]
> http://www.eby-sarna.com/mailman/listinfo/peak