Re: [Scons-dev] Python3 activity

Hi Vasily, On 25.01.2016 21:39, Vasily wrote: Any answer to my question about the place and approach for stubprocess to live in? Thanks, Vasily 16 янв. 2016 г. 0:17 пользователь "Vasily" mailto:just.one@yandex.ru>> написал: I have started looking into the docs for integrating stubpro

Re: [Scons-dev] Python3 activity

I would personally make it a separate file. I'm a very OOP-centric geek. V/R, William On Mon, Jan 25, 2016 at 8:39 PM, Vasily wrote: > Any answer to my question about the place and approach for stubprocess to > live in? > > Thanks, > Vasily > 16 янв. 2016 г. 0:17 пользователь "Vasily" > написа

Re: [Scons-dev] Python3 activity

Any answer to my question about the place and approach for stubprocess to live in? Thanks, Vasily 16 янв. 2016 г. 0:17 пользователь "Vasily" написал: > I have started looking into the docs for integrating stubprocess in there. > > My current thoughts are to put it as a separate file next to posi

Re: [Scons-dev] Python 3 strategy

+1 what Dirk & Gary said with the following addition. If you're going to start from default again, then branch to a different python3 branch "python3-futurize". Otherwise if someone will take a look at https://bitbucket.org/scons/scons/pull-requests/298/fix-for-tigris-bug-2622-alwaysbuild-msvc/dif

Re: [Scons-dev] Python 3 strategy

Hi there, On 25.01.2016 10:39, Russel Winder wrote: I am having difficulty making a decision… The earlier Python 3 branch is founded on using six. At the time a good decision. Now however we have agreed that 2.7 is the base version and thus future rather than six is the better tool for Python 3

Re: [Scons-dev] Python 3 strategy

> On Jan 25, 2016, at 05:29 , William Blevins wrote: > > > > On Mon, Jan 25, 2016 at 9:39 AM, Russel Winder > wrote: > I am having difficulty making a decision… > > The earlier Python 3 branch is founded on using six. At the time a good > decision. Now however we

Re: [Scons-dev] Python 3 strategy

Yeah we wouldn't delete the current changes. On Jan 25, 2016 3:22 PM, "Gary Oberbrunner" wrote: > > On Mon, Jan 25, 2016 at 4:39 AM, Russel Winder > wrote: > >> The alternative is to abandon the current python3-port and start again >> from default based solely on future. >> > > This doesn't seem

Re: [Scons-dev] Python 3 strategy

On Mon, Jan 25, 2016 at 4:39 AM, Russel Winder wrote: > The alternative is to abandon the current python3-port and start again > from default based solely on future. > This doesn't seem crazy to me, although there was a LOT of hand-tweaking of code on the current python3 branch: utf8/locale stuf

Re: [Scons-dev] CI stuff

Russel, Let me contact drone.io and see if we can get a free open source account? I know I spoke with another CI vendor and they said they'd be willing to. Are you currently developing on a branch, or default? -Bill On Mon, Jan 25, 2016 at 3:51 AM, Russel Winder wrote: > On Mon, 2016-01-25 at

[Scons-dev] CI, Semaphore, Shippable

It appears that everyone in the "in the cloud" CI game other than Codeship and Drone assume that all repositories on BitBucket are Git ones. I have asked Drone for special dispensation for long test times for SCons repositories. -- Russel.

Re: [Scons-dev] Python 3 strategy

On Mon, Jan 25, 2016 at 9:39 AM, Russel Winder wrote: > I am having difficulty making a decision… > > The earlier Python 3 branch is founded on using six. At the time a good > decision. Now however we have agreed that 2.7 is the base version and > thus future rather than six is the better tool fo

[Scons-dev] Python 3 strategy

I am having difficulty making a decision… The earlier Python 3 branch is founded on using six. At the time a good decision. Now however we have agreed that 2.7 is the base version and thus future rather than six is the better tool for Python 3. This brings into doubt the python3-port branch as a g

[Scons-dev] Mercurial remote tracking

HgView shows remote tracking branches. Pity HgView is a Qt application rather than a GTK+ one: it looks horrible on my screen, especially compared to gitg. I still prefer the Git transient branch model to the Mercurial persistent branch model. -- Russel. =

Re: [Scons-dev] On CI

On Jan 25, 2016 6:57 AM, "Russel Winder" wrote: > > Independent of any CI Bill is running with Buildbot, I think we should > make use of any and all CI that Atlassian and others connect to > BitBucket, in the same way TravisCI etc. connect into GitHub. > > Having three or four CI instances all mon

Re: [Scons-dev] CI stuff

On Mon, 2016-01-25 at 08:42 +, Russel Winder wrote: > Codeshio.ip shows a very sensible ignore and fail lists, in that it > concurs with my local builds. :-) > > Lots of work to be done. For me the real irritant is why the mkfifo > test fails. > > Drone.io bombs out after 15 minutes on free a

[Scons-dev] CI stuff

Codeshio.ip shows a very sensible ignore and fail lists, in that it concurs with my local builds. :-) Lots of work to be done. For me the real irritant is why the mkfifo test fails. Drone.io bombs out after 15 minutes on free accounts, SCons tests take longer than 15 minutes. -- Russel. ===

[Scons-dev] On the state of CI

I have a Drone.io account and have set up a Python 2.7 test CI on it for my SCons__Python3 repository and the python3-port branch. It's very red.  https://drone.io/bitbucket.org/russel/scons__python3 I have created Shippable and Semaphoe accounts, but there is no CI as yet because they cannot see