<div dir="ltr">Hi Ivan, all,<div><br></div><div>I have installed Rivet and Yoda on a system with Python3 (i.e. /usr/bin/python is version 3.7) and it generally works. So there is no lack of Python3 versions per se.</div><div><br></div><div>But there are a few small remaining issues I noticed during some simple tests:</div><div><br></div><div>- rivet-mkhtml needs to get rid of a few '.encode("utf-8")' instances<br></div><div>Here it's not completely clear to me whether this is backward compatible to Python2.</div><div><br></div><div>- bin/make-plots needs to be treated to a '2to3 -w make-plots' conversion.</div><div>Same as above, but I think it should be fine.</div><br class="gmail-Apple-interchange-newline"><div>- there is an error in yodamerge where I'm not actually sure whether it's a problem with Python3 or just a change in the YODA API:<br></div><div>$ yodamerge Rivet.yoda Rivet1.yoda </div><div>Traceback (most recent call last):<br></div><div> File "/usr/bin/yodamerge", line 274, in <module></div><div> ao_out.points[i].setErrs(dim , (ep_i[var], em_i[var]),var)</div><div> File "include/Point.pyx", line 75, in yoda.core.Point.setErrs</div><div> File "stringsource", line 147, in pair.from_py.__pyx_convert_pair_from_py_double__and_double</div><div>TypeError: must be real number, not tuple</div><div>YODA developers might be able to tell right away?<br></div><div><br></div><div>So if you in Genser have some experience with Python2 vs. 3 maintenance and can provide advise on the backward compatibility etc of e.g. the changes above (and further testing), then I'm happy to follow up and dust off my (little) Mercurial knowledge to get the remaining Python3 changes into the Rivet repo.</div><div><br></div><div>Best,</div><div>Frank</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, 14 Aug 2018 at 18:09, Andy Buckley <<a href="mailto:andy.buckley@cern.ch">andy.buckley@cern.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi Ivan,</div><br><div>We won't be releasing/maintaining separate codebases, but I think the libraries should now be Python3 compatible: Frank Siegert did a lot of compatibility work and I think is using Py3 personally. I noticed recently that we are still using optparse rather than argparse for command-line option parsing in the scripts, but maybe that has been worked around... I'll let him comment.</div><br><div>Cheers,</div><div>Andy</div><br><div><u></u><div><table cellpadding="0" cellspacing="0"><tbody><tr><td colspan="2"><div style="padding-bottom:15px"><div><strong>Dr Andy Buckley, Senior Lecturer / Royal Society University Research Fellow</strong></div><div>Particle Physics Experiment Group, University of Glasgow</div></div></td></tr><tr><td style="vertical-align:top"></td><td><div style="font-size:0.9em;white-space:nowrap;border-left:2px solid gray;margin-left:20px;padding-left:20px"><div><div></div><div></div></div></div></td></tr></tbody></table></div><u></u></div><div class="m_6589600028659671641gmail_quote_attribution">On Aug 14 2018, at 4:34 pm, Ivan Razumov <<a href="mailto:ivan.razumov@cern.ch" target="_blank">ivan.razumov@cern.ch</a>> wrote:</div><blockquote><br><div><br><div><font size="1">Dear Rivet developers,</font></div><br><div><div><font size="1">we have noticed the lack of Python3 versions for the new release of Rivet and Yoda. It this intentional (i.e. the code is now compatible with both Python2 and Python3),</font></div><div><font size="1">or they will be released later?</font></div></div><br><div><div><font size="1">Thanks,</font></div><div><font size="1">Ivan for the GENSER team</font></div></div><div>_______________________________________________</div><div>Rivet mailing list</div><div><a href="mailto:Rivet@projects.hepforge.org" target="_blank">Rivet@projects.hepforge.org</a></div><div><a href="https://www.hepforge.org/lists/listinfo/rivet" target="_blank">https://www.hepforge.org/lists/listinfo/rivet</a></div></div></blockquote></blockquote></div>