[Rivet] python2 change

[Andy Buckley]

On 12/05/14 15:08, Frank Siegert wrote:
> Ok, so I suggest I create a private repo with the changes I have done
> so far, and then we can decide how to implement them such that they
> are compatible with Python2 (either with explicit switches or with
> from __future__). I would need to do this for both YODA and Rivet, and
> the m4/ external though.

Sounds good to me.

> As far as I remember, I log in to HepForge and then simply clone the
> master into /hepforge/hg/<project>/private, right? What about the m4
> externals?

If I remember correctly they are not externals anymore. They evolved as
shared externals in "the SVN era" and I think that was the right thing
to do as we worked out what were good and bad ideas. Now I think they
are just normal files, separately stored in each repo and rarely
updated... although IMO it's a good idea to manually sync good changes
between them.

Andy


> On 12 May 2014 14:59, David Grellscheid <david.grellscheid at durham.ac.uk> wrote:
>> Hi Andy,
>>
>>
>>> Being able to assume Python 2.6.6 or later would make the migration far
>>> easier, I think. I'm personally happy to drop support for SL5 now: the
>>> whole Grid has managed to switch to SL6 so individuals have ~no excuse!
>>
>>
>> I agree with dropping SL5. Python 2.6 came out in 2008 and makes the
>> transition very easy with many "from __future__" helpers already provided.
>>
>>
>>> I don't know if there are many "standard" systems out there with Python
>>> 2.5. What versions are installed on current/recent Macs?
>>
>>
>> Mavericks has 2.7.5, so no problem there. Mac owners typically upgrade
>> fairly quickly.
>>
>>   David
>>
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> https://www.hepforge.org/lists/listinfo/rivet


-- 
Dr Andy Buckley, Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow / PH Dept, CERN