Re: PEAK-Rules for Python3
Hervé Coatanhay <[email protected]> Tue, 17 Mar 2015 12:23:45 +0100
| Newsgroups | gmane.comp.python.peak |
|---|---|
| Message-ID | <[email protected]> |
--===============1265687947== Content-Type: multipart/alternative; boundary="Apple-Mail=_77D0CB36-B2C8-4E78-A43E-95CBABE206F4" --Apple-Mail=_77D0CB36-B2C8-4E78-A43E-95CBABE206F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Cara, My attempt is stil available here = https://bitbucket.org/Alzakath/peak-py3 = <https://bitbucket.org/Alzakath/peak-py3>. -- Herv=C3=A9 > Le 17 mars 2015 =C3=A0 03:30, Cara <[email protected]> = a =C3=A9crit : >=20 > I'm investigating trying to get PEAK-Rules running on Python 3. I > know that Herv=C3=A9 Coatanhay attempted this before, but their code = is no > longer up at Bitbucket, so I'm starting from the code in the > repository as is. To make this less unmanageable and since breaking > some backwards compatibility is necessary, I'm planning to use the > futurize script from http://python-future.org/ to try to get the code > base into a state compatible with 2.6+ and 3.3+. If I get anywhere, > would you be interested in integrating patches, or would I have to > fork it? If I do fork it, is there a license file I need to include? > Would the commit logs be sufficient to fulfill the requirements? >=20 > Cara > _______________________________________________ > PEAK mailing list > [email protected] > http://www.eby-sarna.com/mailman/listinfo/peak --Apple-Mail=_77D0CB36-B2C8-4E78-A43E-95CBABE206F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">Hi Cara,<div class=3D""><br class=3D""></div><div class=3D"">My= attempt is stil available here <a = href=3D"https://bitbucket.org/Alzakath/peak-py3" = class=3D"">https://bitbucket.org/Alzakath/peak-py3</a>.</div><div = class=3D""><br class=3D""></div><div class=3D"">--</div><div = class=3D"">Herv=C3=A9</div><div class=3D""><br class=3D""><div><blockquote= type=3D"cite" class=3D""><div class=3D"">Le 17 mars 2015 =C3=A0 03:30, = Cara <<a href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> a =C3=A9crit = :</div><br class=3D"Apple-interchange-newline"><div class=3D"">I'm = investigating trying to get PEAK-Rules running on Python 3. I<br = class=3D"">know that Herv=C3=A9 Coatanhay attempted this before, but = their code is no<br class=3D"">longer up at Bitbucket, so I'm starting = from the code in the<br class=3D"">repository as is. To make this = less unmanageable and since breaking<br class=3D"">some backwards = compatibility is necessary, I'm planning to use the<br class=3D"">futurize= script from <a href=3D"http://python-future.org/" = class=3D"">http://python-future.org/</a> to try to get the code<br = class=3D"">base into a state compatible with 2.6+ and 3.3+. If I = get anywhere,<br class=3D"">would you be interested in integrating = patches, or would I have to<br class=3D"">fork it? If I do fork = it, is there a license file I need to include?<br class=3D"">Would the = commit logs be sufficient to fulfill the requirements?<br class=3D""><br = class=3D"">Cara<br = class=3D"">_______________________________________________<br = class=3D"">PEAK mailing list<br class=3D""><a = href=3D"mailto:[email protected]" class=3D"">[email protected]</a><br = class=3D"">http://www.eby-sarna.com/mailman/listinfo/peak<br = class=3D""></div></blockquote></div><br class=3D""></div></body></html>= --Apple-Mail=_77D0CB36-B2C8-4E78-A43E-95CBABE206F4-- --===============1265687947== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PEAK mailing list [email protected] http://www.eby-sarna.com/mailman/listinfo/peak --===============1265687947==--