Next thing is to merge default into the python3 branch. I did this a few
months ago; you can look at the merge to see the kinds of things that have
to be tweaked, it's not usually too bad.
On Tue, Sep 22, 2015 at 3:44 PM, Tim Jenness wrote:
>
> > On Sep 22, 2015, at 12:33 ,
> On Sep 22, 2015, at 12:33 , Bill Deegan wrote:
>
> Tim,
>
> Feel free to help out on the python 3 work then.
>
Ok. Where do I start? (I’m trying to get a buildbot slave set up but the
process of locating a linux machine is taking a while).
Last time I looked
Tim,
Feel free to help out on the python 3 work then.
-Bill
On Mon, Sep 21, 2015 at 9:13 PM, Tim Jenness wrote:
>
> > On Sep 21, 2015, at 20:09 , Bill Deegan
> wrote:
> >
> > William,
> >
> > Sounds good.
> > I'd like to make sure we get some
Hi there,
On 22.09.2015 05:09, Bill Deegan wrote:
William,
Sounds good.
I'd like to make sure we get some performance profiling before/after such
changes to make sure we don't slow SCons down.
I volunteer to weed out some of the old Python 2.x stuff (where x < 7 ;) ) on a separate bug
Sounds good. I have used that suite before. I will have to set it back up
on this machine. I may have some questions about required tools. Not sure
if I could get all 3 profiler steps working.
V/R,
William
On Tue, Sep 22, 2015 at 8:13 AM, Dirk Bächle wrote:
> Hi there,
>
>