I'll see if I can get a package up on sourceforge in the next day or so.
Be warned it's alpha.
There's still a couple unresolved regression failures.
-Bill
On Wed, Jun 7, 2017 at 4:10 AM, Tim Jenness wrote:
> This is great. Sorry for the daft question, but how do I get a tar
On Tue, 2017-06-06 at 18:51 +0100, Russel Winder wrote:
> On Tue, 2017-06-06 at 13:33 -0400, Bill Deegan wrote:
> > Py 3.5 or 3.6?
> > Excellent!
>
> I'm currently on Debian Sid so sadly only 3.5.3. I'll switch to
> Fedora
> Rawhide for tomorrow and that is 3.6.?
SCons working fine using Python
This is great. Sorry for the daft question, but how do I get a tar file of the
scons 3 alpha code that looks like a standard scons tar distribution? I have
cloned the mercurial repo but I can’t find out in the READMEs how to go from
the cloned repo to a distribution tar file. I want the tar
On Tue, 2017-06-06 at 13:33 -0400, Bill Deegan wrote:
> Py 3.5 or 3.6?
> Excellent!
I'm currently on Debian Sid so sadly only 3.5.3. I'll switch to Fedora
Rawhide for tomorrow and that is 3.6.?
If you do not get bug reports from me, you know Python 3 is working
fine running SCons default/tip.
Py 3.5 or 3.6?
Excellent!
On Tue, Jun 6, 2017 at 1:01 PM, Russel Winder wrote:
> On Tue, 2017-06-06 at 11:35 -0400, Bill Deegan wrote:
> > Remove your .sconsign file and run again.
> >
> > It's still on the to fix list..
>
> :-)
>
> OK, I am now a "Using SCons with Python
On Tue, 2017-06-06 at 11:35 -0400, Bill Deegan wrote:
> Remove your .sconsign file and run again.
>
> It's still on the to fix list..
:-)
OK, I am now a "Using SCons with Python 3" person.
--
Russel.
=
Dr Russel
Remove your .sconsign file and run again.
It's still on the to fix list..
-Bill
On Tue, Jun 6, 2017 at 11:31 AM, Russel Winder wrote:
> On Mon, 2017-06-05 at 14:03 -0400, Bill Deegan wrote:
> > Run --debug=stacktrace and post stacktrace?
>
>
> scons: Reading SConscript
On Mon, 2017-06-05 at 14:03 -0400, Bill Deegan wrote:
> Run --debug=stacktrace and post stacktrace?
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
scons: *** [Build/UnitTests/unit-test] UnicodeDecodeError : 'ascii' codec can't
decode byte
Run --debug=stacktrace and post stacktrace?
On Mon, Jun 5, 2017 at 12:05 PM, Russel Winder wrote:
> On Mon, 2017-06-05 at 17:46 +0200, Tim Jenness wrote:
> > Limited network access but does your file have a BOM? If the first
> > character in the file is something like
On Mon, 2017-06-05 at 17:46 +0200, Tim Jenness wrote:
> Limited network access but does your file have a BOM? If the first
> character in the file is something like that you can't use ascii to
> read it.
>
First character is definitely an i as in import – well that is what od
-c tells me
Limited network access but does your file have a BOM? If the first character
in the file is something like that you can't use ascii to read it.
Sent from my iPhone
> On Jun 5, 2017, at 17:41, Russel Winder wrote:
>
> I updated to default/tip and tried using Python 2 –
I updated to default/tip and tried using Python 2 – worked fine – and
then Python 3:
|> python3 /home/russel/Repositories/Mercurial/Forks/SCons/src/script/scons.py
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
scons: *** [source/main.d]
Hi Russel,
On 10.04.2016 13:10, Russel Winder wrote:
The python3-port currently has:
47 test fails
108 no results
[...]
Sorry I didn't get much done on this over the last 12 weeks, long (and
tedious) story – which no-one is interested in.
you have done a lot...by starting the task and
The python3-port currently has:
47 test fails
108 no results
running the tests using Python 2.7.11 on Fedora Rawhide.
The tests don't really start using Python 3.5.1 because of stuff to do
with UserDict.
I believe the Python 3 stuff can actually wait until the tests all pass
using Python 2.
Dirk,
I'll take a look at windows. It does seem a bit odd..
-Bill
On Sat, Dec 19, 2015 at 4:12 AM, Dirk Bächle wrote:
> Russel,
>
> On 19.12.2015 10:39, Russel Winder wrote:
>
>> On Wed, 2015-12-16 at 09:22 +0100, Dirk Bächle wrote:
>>
>>>
>>> […]
>>
>>> @Russel: If all
Hi Russel; last time I did this it wasn't all _that_ painful. Took a few
hours if I remember rightly. (Of course a lot of time has passed, but still
not that much new code compared to the entire code base.) Look at the diff
of the last merge before you start, to get a sense of the top two or three
Hi all,
On 15.12.2015 23:07, Bill Deegan wrote:
Dirk,
Looks like the pull request blew up windows testing..
http://buildbot.scons.org/builders/win7-64-vs20102.7/builds/257/steps/shell/logs/stdio
I fixed the problem directly on the trunk. Buildbots are still running, but it
looks much
+1 for just merging the patch
On Tue, Dec 15, 2015 at 3:36 AM, Bill Deegan
wrote:
> Dirk,
>
> I think we've given enough notice that pre 2.7 is going to be dropped.
> I'll take a pass through the updated pull request (#284) and merge it,
> unless someone has serious
Dirk,
Looks like the pull request blew up windows testing..
http://buildbot.scons.org/builders/win7-64-vs20102.7/builds/257/steps/shell/logs/stdio
Do you have access to a machine to take a look?
-Bill
On Tue, Dec 15, 2015 at 7:08 AM, William Blevins
wrote:
> +1 for
Bill,
On 15.12.2015 23:07, Bill Deegan wrote:
Dirk,
Looks like the pull request blew up windows testing..
http://buildbot.scons.org/builders/win7-64-vs20102.7/builds/257/steps/shell/logs/stdio
sorry for that.
Do you have access to a machine to take a look?
I'd have to fire up one of
Bill,
On 15.12.2015 23:07, Bill Deegan wrote:
Dirk,
Looks like the pull request blew up windows testing..
http://buildbot.scons.org/builders/win7-64-vs20102.7/builds/257/steps/shell/logs/stdio
Do you have access to a machine to take a look?
just gave this another short look, and I think I
Dirk,
I think we've given enough notice that pre 2.7 is going to be dropped.
I'll take a pass through the updated pull request (#284) and merge it,
unless someone has serious issues with doing so.
-Bill
On Mon, Dec 14, 2015 at 4:53 PM, Dirk Bächle wrote:
> Hi there,
>
> On
Dirk is working on a pull request for pre-2.7 cleanup in the default
branch.
https://bitbucket.org/scons/scons/pull-requests/284/code-cleanup-removed-several-pre-27
You might want to wait until after or just realize that you will need to
merge again after.
V/R,
William
On Fri, Dec 11, 2015 at
+1 on waiting for Dirks pull request to land.
He has a couple items to add before it's complete.
He said he'll be working on them over the weekend.
Might be done by Tuesday..
-Bill
On Fri, Dec 11, 2015 at 8:09 AM, William Blevins
wrote:
> Dirk is working on a pull
I may well do a new merge of default branch into python3 branch on
Tuesday next and see what the fallout is. Unless someone knows any
reason why I should not or that I should delay.
--
Russel.
=
Dr Russel Winder t:
William,
Yes bitbucket pull requests are looked at.
Some non-trivial ones (such as yours), require a good block of time to do a
thorough review prior to merging.
-Bill
On Thu, Sep 10, 2015 at 9:16 AM, William Blevins
wrote:
>
>
> On Wed, Sep 9, 2015 at 2:27 PM, Bill
There is a flurry of activity on porting Bazaar so it run on Python
2.6+ and Python 3. There seems to be a consensus that assuming 3.4 as
the base Python 3 version is a good idea.
SCons already assumes Python 2.7, but is there a base bugfix version?
This matters as it determines how much of
> On Sep 9, 2015, at 10:16 , Russel Winder wrote:
>
> There is a flurry of activity on porting Bazaar so it run on Python
> 2.6+ and Python 3. There seems to be a consensus that assuming 3.4 as
> the base Python 3 version is a good idea.
>
> SCons already assumes Python
SCons supports >=2.7 <3.0
As far as I know, the idea was to not break 2.6 if it was reasonable not
to, but no guarantee.
Clearly starting work on 2.7 & 3.0 compatible source code would mean 2.6
would be dropped entirely.
I've not read the release notes on 2.7.*, is there some significant
I am assuming we would be wise to merge default into python3-port to
avoid things getting out of hand?
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm:
The people I am currently doing a series of Python workshops for (*) are
using SCons. They cannot move their Python activity from Python 2 to
Python 3 because of a one version of Python rule and the fact that
SCons only currently works with Python 2.
I have suggested they chip in £50,000 to fund
Can you estimate the efforts that you spend porting Python 2
SConstruct to Python 3? This info IMHO is very critical for existing
SCons users who are not aware of Python 2/3 portability issues. We
will have to create a separate porting guide for those SCons users,
who are not Python hackers like
Is it correct that no-one has been keeping the Python 3 branch up to
date with all the changes that have gone into default?
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41
I plan to merge things in soon. I have some local changes already so
I think I'm the best one to do it.
On Mon, Mar 10, 2014 at 1:06 PM, Russel Winder rus...@winder.org.uk wrote:
Is it correct that no-one has been keeping the Python 3 branch up to
date with all the changes that have gone into
34 matches
Mail list logo