Hi folks,

I’ve committed a couple of draft pull requests to the master branch
regarding a couple of issues I see regularly when trying to test.

I run code in LXD containers (Like docker, but not), to stop conflicts and
stuff with other code on the same boxes. For some reason, for which I’m not
entirely sure, but LXD bash doesn’t like the shopt stuff in the PGE, the
only use for it that I can see is the rat alias in PreConfig_Rat.xml, so
one PR removes the alias and swaps it for a shell function that should be
more portable and make my testing life easier.

The other more sizeable change is a breaking change to go from Python 2 to
Python 3. It builds and runs locally and on my LXD containers with the
above PR combined, personally I’d like to see a swap to Python 3 mostly
cause installing Python 2 isn’t default most of the time these days and so
figuring out why DRAT bombed when you don’t realise it uses Python 2 is a
bit of a pain.

Anyway, I bring them up here because they need testing ideally and also
some discussion about when/if they get merged etc because are they pre or
post 1.0?

Cheers

Tom

-- 


Spicule Limited is registered in England & Wales. Company Number: 
09954122. Registered office: First Floor, Telecom House, 125-135 Preston 
Road, Brighton, England, BN1 6AF. VAT No. 251478891.




All engagements 
are subject to Spicule Terms and Conditions of Business. This email and its 
contents are intended solely for the individual to whom it is addressed and 
may contain information that is confidential, privileged or otherwise 
protected from disclosure, distributing or copying. Any views or opinions 
presented in this email are solely those of the author and do not 
necessarily represent those of Spicule Limited. The company accepts no 
liability for any damage caused by any virus transmitted by this email. If 
you have received this message in error, please notify us immediately by 
reply email before deleting it from your system. Service of legal notice 
cannot be effected on Spicule Limited by email.

Reply via email to