Re: [Scons-dev] SCons and Python 3
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 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 file so > I can test in my Jenkins system in the same way as I use earlier scons > releases. > > Thanks > > — > Tim Jenness > > > On Jun 6, 2017, at 19:01 , 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 3" person. > > > > -- > > Russel. > > > = > > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:russel.win...@ekiga.net > > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > ___ > > Scons-dev mailing list > > Scons-dev@scons.org > > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 3.6.1 on Fedora Rawhide. > If you do not get bug reports from me, you know Python 3 is working > fine running SCons default/tip. > -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 file so I can test in my Jenkins system in the same way as I use earlier scons releases. Thanks — Tim Jenness > On Jun 6, 2017, at 19:01 , 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 3" person. > > -- > Russel. > = > Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 3" person. > > -- > Russel. > > = > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 files ...
> scons: done reading SConscript files.
> scons: Building targets ...
> scons: *** [Build/UnitTests/unit-test] UnicodeDecodeError : 'ascii' codec
> can't decode byte 0x80 in position 0: ordinal not in range(128)
> scons: internal stack trace:
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Job.py", line 199, in start
> task.prepare()
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Script/Main.py", line 175, in prepare
> return SCons.Taskmaster.OutOfDateTask.prepare(self)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Taskmaster.py", line 176, in prepare
> self.exception_raise()
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Taskmaster.py", line 551, in _exception_raise
> exec("raise exc_value.with_traceback(exc_traceback)")
> File "", line 1, in
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Taskmaster.py", line 971, in next_task
> task.make_ready()
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Script/Main.py", line 309, in make_ready
> SCons.Taskmaster.OutOfDateTask.make_ready(self)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Taskmaster.py", line 408, in make_ready_current
> (not t.always_build and t.is_up_to_date())
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Node/FS.py", line 3248, in is_up_to_date
> self.changed()
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Node/FS.py", line 3192, in changed
> has_changed = SCons.Node.Node.changed(self, node)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Node/__init__.py", line 1455, in changed
> bi = node.get_stored_info().binfo
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Node/FS.py", line 2801, in get_stored_info
> sconsign_entry = self.dir.sconsign().get_entry(self.name)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Node/FS.py", line 1840, in sconsign
> return _sconsign_map[self._func_sconsign](self)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/Node/FS.py", line 71, in sconsign_dir
> node._sconsign = SCons.SConsign.ForDirectory(node)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/SConsign.py", line 234, in __init__
> db, mode = Get_DataBase(dir)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/SConsign.py", line 88, in Get_DataBase
> db = DataBase[top] = DB_Module.open(DB_Name, "c")
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/dblite.py", line 197, in open
> return dblite(file, flag, mode)
> File "/home/users/russel/Repositories/Mercurial/Forks/
> SCons/src/engine/SCons/dblite.py", line 117, in __init__
> self._dict = pickle.loads(p)
> scons: building terminated because of errors.
>
>
> --
> Russel.
>
> =
> Dr Russel Winder t: +44 20 7585 2200 voip:
> sip:russel.win...@ekiga.net
> 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk
> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 0x80 in position 0: ordinal not in range(128)
scons: internal stack trace:
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Job.py",
line 199, in start
task.prepare()
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Script/Main.py",
line 175, in prepare
return SCons.Taskmaster.OutOfDateTask.prepare(self)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Taskmaster.py",
line 176, in prepare
self.exception_raise()
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Taskmaster.py",
line 551, in _exception_raise
exec("raise exc_value.with_traceback(exc_traceback)")
File "", line 1, in
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Taskmaster.py",
line 971, in next_task
task.make_ready()
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Script/Main.py",
line 309, in make_ready
SCons.Taskmaster.OutOfDateTask.make_ready(self)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Taskmaster.py",
line 408, in make_ready_current
(not t.always_build and t.is_up_to_date())
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Node/FS.py",
line 3248, in is_up_to_date
self.changed()
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Node/FS.py",
line 3192, in changed
has_changed = SCons.Node.Node.changed(self, node)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Node/__init__.py",
line 1455, in changed
bi = node.get_stored_info().binfo
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Node/FS.py",
line 2801, in get_stored_info
sconsign_entry = self.dir.sconsign().get_entry(self.name)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Node/FS.py",
line 1840, in sconsign
return _sconsign_map[self._func_sconsign](self)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/Node/FS.py",
line 71, in sconsign_dir
node._sconsign = SCons.SConsign.ForDirectory(node)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/SConsign.py",
line 234, in __init__
db, mode = Get_DataBase(dir)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/SConsign.py",
line 88, in Get_DataBase
db = DataBase[top] = DB_Module.open(DB_Name, "c")
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/dblite.py",
line 197, in open
return dblite(file, flag, mode)
File
"/home/users/russel/Repositories/Mercurial/Forks/SCons/src/engine/SCons/dblite.py",
line 117, in __init__
self._dict = pickle.loads(p)
scons: building terminated because of errors.
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 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 anyway! > > As far as I am aware Linux UTF-8 filestores never use BOMs. However > this is going to be an issue for Windows UCS2 filestores. > > -- > Russel. > > = > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 anyway! As far as I am aware Linux UTF-8 filestores never use BOMs. However this is going to be an issue for Windows UCS2 filestores. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 – 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] UnicodeDecodeError : 'ascii' codec can't decode > byte 0x80 in position 0: ordinal not in range(128) > scons: building terminated because of errors. > > > As far as I am aware, source/main.d is a UTF-8 encoded file containing > only ASCII characters. I am not sure how to debug this, but I can take > a punt with some direction. > > -- > Russel. > = > Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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] UnicodeDecodeError : 'ascii' codec can't decode byte 0x80 in position 0: ordinal not in range(128) scons: building terminated because of errors. As far as I am aware, source/main.d is a UTF-8 encoded file containing only ASCII characters. I am not sure how to debug this, but I can take a punt with some direction. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 keeping development and the discussion about it alive. Thanks for all the effort you've put into this so far! Best regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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. Then it can be full steam ahead on making it work with Python 3 as well. The foundation is there and using future I think it should all be fairly straightforward. This will mean that Python 2.7 really is the base version of Python and so all the 2.6 and earlier stuff will need to go if there is any left. Sorry I didn't get much done on this over the last 12 weeks, long (and tedious) story – which no-one is interested in. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 Buildbots turn out to be "green", feel free to merge >>> onto the python3 branch... >>> >> >> It appears as though Windows is still a bit red, but I cannot in all >> honest profess any sadness. >> > > feel free to latch on. The Windows bot seems to have had a "hiccup"...it > didn't find any updates on its last "hg pull", but the last proper run was > green. @Bill: Can you check the Windows setup? It looks to me as if it has > a problem with merges over more than one commit. The slave seems to think > that it has to process several commits, but pulls all of them in the first > run anyway? That's how it looks to me at least... > > As all the Linux variants are green, I > >> shall take this as a "go" to do a merge to the Python 3 branch. This >> will undoubtedly lead to a right royal mess, but then that is the whole >> point – fix the mess. >> >> My assumptions will be: >> >> Python 3.4 and 3.5 >> Python 2.7.10 >> Debian Sid >> Fedora Rawhide >> No packages not in the standard distribution >> A lack of CI to cover Solaris, OSX or Windows >> >> > Sounds good. > > I may be gone a while… >> >> Progress will be reflected in https://bitbucket.org/russel/scons__pyth >> on3 >> >> > I'll definitely track that one. If you need help, just let us know...I'm > sure that all the other devs (me included) are ready to jump in and help > where they can. > > Meanwhile, we others should try to come up with a plan of how to test > Python 2.7 and 3.x in parallel in the future. Some people have nominated > "tox" for this task already, but is this still the way to go...or can > anybody recommend a better tool? > > Best regards, > > > Dirk > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 things that have to get tweaked. On Sat, Dec 19, 2015 at 4:39 AM, Russel Winder wrote: > On Wed, 2015-12-16 at 09:22 +0100, Dirk Bächle wrote: > > > […] > > @Russel: If all Buildbots turn out to be "green", feel free to merge > > onto the python3 branch... > > It appears as though Windows is still a bit red, but I cannot in all > honest profess any sadness. As all the Linux variants are green, I > shall take this as a "go" to do a merge to the Python 3 branch. This > will undoubtedly lead to a right royal mess, but then that is the whole > point – fix the mess. > > My assumptions will be: > > Python 3.4 and 3.5 > Python 2.7.10 > Debian Sid > Fedora Rawhide > No packages not in the standard distribution > A lack of CI to cover Solaris, OSX or Windows > > I may be gone a while… > > Progress will be reflected in https://bitbucket.org/russel/scons__pyth > on3 > > Should anyone track progress and want to chip in feel free. If you see > any lack of progress, it will either be me having to work on organizing > ACCU 2016 (accu.org) or choosing to work for a while on GPars or Me TV > – or eating and especially drinking, it is Christmas after all. Do not > drink and code. > > -- > Russel. > > = > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > -- Gary ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 Buildbots turn out to be "green", feel free to merge onto the python3 branch... It appears as though Windows is still a bit red, but I cannot in all honest profess any sadness. feel free to latch on. The Windows bot seems to have had a "hiccup"...it didn't find any updates on its last "hg pull", but the last proper run was green. @Bill: Can you check the Windows setup? It looks to me as if it has a problem with merges over more than one commit. The slave seems to think that it has to process several commits, but pulls all of them in the first run anyway? That's how it looks to me at least... As all the Linux variants are green, I shall take this as a "go" to do a merge to the Python 3 branch. This will undoubtedly lead to a right royal mess, but then that is the whole point – fix the mess. My assumptions will be: Python 3.4 and 3.5 Python 2.7.10 Debian Sid Fedora Rawhide No packages not in the standard distribution A lack of CI to cover Solaris, OSX or Windows Sounds good. I may be gone a while… Progress will be reflected in https://bitbucket.org/russel/scons__pyth on3 I'll definitely track that one. If you need help, just let us know...I'm sure that all the other devs (me included) are ready to jump in and help where they can. Meanwhile, we others should try to come up with a plan of how to test Python 2.7 and 3.x in parallel in the future. Some people have nominated "tox" for this task already, but is this still the way to go...or can anybody recommend a better tool? Best regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
On Wed, 2015-12-16 at 09:22 +0100, Dirk Bächle wrote: > […] > @Russel: If all Buildbots turn out to be "green", feel free to merge > onto the python3 branch... It appears as though Windows is still a bit red, but I cannot in all honest profess any sadness. As all the Linux variants are green, I shall take this as a "go" to do a merge to the Python 3 branch. This will undoubtedly lead to a right royal mess, but then that is the whole point – fix the mess. My assumptions will be: Python 3.4 and 3.5 Python 2.7.10 Debian Sid Fedora Rawhide No packages not in the standard distribution A lack of CI to cover Solaris, OSX or Windows I may be gone a while… Progress will be reflected in https://bitbucket.org/russel/scons__pyth on3 Should anyone track progress and want to chip in feel free. If you see any lack of progress, it will either be me having to work on organizing ACCU 2016 (accu.org) or choosing to work for a while on GPars or Me TV – or eating and especially drinking, it is Christmas after all. Do not drink and code. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 better now. @Russel: If all Buildbots turn out to be "green", feel free to merge onto the python3 branch... Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 know what's wrong: src/engine/SCons/Util.py, make ll. 587 look like this if can_read_reg: WinError = WindowsError HKEY_CLASSES_ROOT = hkey_mod.HKEY_CLASSES_ROOT such that Util.WinError gets also initialized if we can read the registry. That should help. ;) Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 my old Windows XP boxes under kvm/VirtualBox and see if I can reproduce the error...not sure if this is a good idea though, because it would only have MinGW installed...but no VisualStudio of any kind. And I'm not sure that I have a decent Python 2.7.x in there, might be only 2.6, arrghh. I would also get to this tomorrow night earliest, it's pretty late here already. So if you can take a look, I don't mind you (or someone else) taking over... ;) Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 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 issues with doing so. >> >> -Bill >> >> >> On Mon, Dec 14, 2015 at 4:53 PM, Dirk Bächle wrote: >> >>> Hi there, >>> >>> On 11.12.2015 22:39, Bill Deegan wrote: >>> +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.. >>> I've updated my pull request with an additional commit. So, short of a >>> final review, it should be ready to get merged... >>> >>> I'd like to raise one question though: What about the integration of the >>> "stubprocess.py" wrapper? Wasn't this planned for the next release 2.5? If >>> we want to keep it this way, it might be better to *not* merge my PR into >>> "trunk" right now, but only onto the python3 branch directly. >>> Like this, we could work on the "stubprocess" thingy, merge it to >>> "trunk" first, and only then put PR#284 on top. This would give us the >>> opportunity to release a 2.5 with the "stubprocess.py" speedup, but still >>> (some) backward compatibility to Python 2.6...so more users could benefit >>> from this? >>> >>> Just as an idea... >>> >>> Best regards, >>> >>> Dirk >>> >>> >>> >>> ___ >>> Scons-dev mailing list >>> Scons-dev@scons.org >>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>> >> >> >> ___ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
+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 issues with doing so. > > -Bill > > > On Mon, Dec 14, 2015 at 4:53 PM, Dirk Bächle wrote: > >> Hi there, >> >> On 11.12.2015 22:39, Bill Deegan wrote: >> >>> +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.. >>> >>> >> I've updated my pull request with an additional commit. So, short of a >> final review, it should be ready to get merged... >> >> I'd like to raise one question though: What about the integration of the >> "stubprocess.py" wrapper? Wasn't this planned for the next release 2.5? If >> we want to keep it this way, it might be better to *not* merge my PR into >> "trunk" right now, but only onto the python3 branch directly. >> Like this, we could work on the "stubprocess" thingy, merge it to "trunk" >> first, and only then put PR#284 on top. This would give us the opportunity >> to release a 2.5 with the "stubprocess.py" speedup, but still (some) >> backward compatibility to Python 2.6...so more users could benefit from >> this? >> >> Just as an idea... >> >> Best regards, >> >> Dirk >> >> >> >> ___ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 11.12.2015 22:39, Bill Deegan wrote: > >> +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.. >> >> > I've updated my pull request with an additional commit. So, short of a > final review, it should be ready to get merged... > > I'd like to raise one question though: What about the integration of the > "stubprocess.py" wrapper? Wasn't this planned for the next release 2.5? If > we want to keep it this way, it might be better to *not* merge my PR into > "trunk" right now, but only onto the python3 branch directly. > Like this, we could work on the "stubprocess" thingy, merge it to "trunk" > first, and only then put PR#284 on top. This would give us the opportunity > to release a 2.5 with the "stubprocess.py" speedup, but still (some) > backward compatibility to Python 2.6...so more users could benefit from > this? > > Just as an idea... > > Best regards, > > Dirk > > > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
Hi there, On 11.12.2015 22:39, Bill Deegan wrote: +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.. I've updated my pull request with an additional commit. So, short of a final review, it should be ready to get merged... I'd like to raise one question though: What about the integration of the "stubprocess.py" wrapper? Wasn't this planned for the next release 2.5? If we want to keep it this way, it might be better to *not* merge my PR into "trunk" right now, but only onto the python3 branch directly. Like this, we could work on the "stubprocess" thingy, merge it to "trunk" first, and only then put PR#284 on top. This would give us the opportunity to release a 2.5 with the "stubprocess.py" speedup, but still (some) backward compatibility to Python 2.6...so more users could benefit from this? Just as an idea... Best regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
+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 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 12:44 PM, Russel Winder > wrote: > >> 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: +44 20 7585 2200 voip: >> sip:russel.win...@ekiga.net >> 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk >> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >> >> >> ___ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 12:44 PM, Russel Winder wrote: > 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: +44 20 7585 2200 voip: > sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 Deegan > wrote: > >> Tim, >> >> On Wed, Sep 9, 2015 at 10:52 AM, Tim Jenness wrote: >> >>> >>> On Sep 9, 2015, at 10:49 , Bill Deegan >>> wrote: >>> >>> 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. >>> >>> >>> The scons release notes are very specific: >>> >>> >>> This will be the last release to support Python versions earlier than >>> 2.7, as we begin to move toward supporting Python 3. >>> >>> Which reads to me that 2.6 is being dropped and python 3 is to be >>> supported. >>> >> >> This doesn't conflict with what I wrote in any way. >> >> A guarantee that it will work with 2.6 has been removed. As I said >> above, if a change breaks 2.6 (in the recent past) and there was an >> equivalently good way to code it which didn't break 2.6, we'd try to use >> that. That said, I don't think this came up very often. >> And as I said above that, shall we say, suggestion is no longer in effect. >> >> At some point (undefined as in no hard commitment on the date of a >> release which will work with 3.x) in the future 3.x will be supported. >> >> We've got a fairly big change in default (slots), which should released >> sometime in the near future. >> Then we've got another larger functional patch (improved cross language >> scanners, if it's ready). >> > > I take this as evidence that no ones watches the BitBucket pull requests. > It's ready to be announced and looked at. > > >> Also a fix for some issues with versioned shared librareis, and 3.x work >> should happen thereafter. >> After that I expect we'll start moving the code to 3.x and 2.7.x compat. >> >> Anyone want to volunteer some buildslaves for 3.x? >> >> -Bill >> >> >> >> >> >>> >>> — >>> Tim Jenness >>> >>> >>> ___ >>> Scons-dev mailing list >>> Scons-dev@scons.org >>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>> >>> >> >> ___ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
On Wed, Sep 9, 2015 at 2:27 PM, Bill Deegan wrote: > Tim, > > On Wed, Sep 9, 2015 at 10:52 AM, Tim Jenness wrote: > >> >> On Sep 9, 2015, at 10:49 , Bill Deegan wrote: >> >> 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. >> >> >> The scons release notes are very specific: >> >> >> This will be the last release to support Python versions earlier than >> 2.7, as we begin to move toward supporting Python 3. >> >> Which reads to me that 2.6 is being dropped and python 3 is to be >> supported. >> > > This doesn't conflict with what I wrote in any way. > > A guarantee that it will work with 2.6 has been removed. As I said above, > if a change breaks 2.6 (in the recent past) and there was an equivalently > good way to code it which didn't break 2.6, we'd try to use that. That > said, I don't think this came up very often. > And as I said above that, shall we say, suggestion is no longer in effect. > > At some point (undefined as in no hard commitment on the date of a release > which will work with 3.x) in the future 3.x will be supported. > > We've got a fairly big change in default (slots), which should released > sometime in the near future. > Then we've got another larger functional patch (improved cross language > scanners, if it's ready). > I take this as evidence that no ones watches the BitBucket pull requests. It's ready to be announced and looked at. > Also a fix for some issues with versioned shared librareis, and 3.x work > should happen thereafter. > After that I expect we'll start moving the code to 3.x and 2.7.x compat. > > Anyone want to volunteer some buildslaves for 3.x? > > -Bill > > > > > >> >> — >> Tim Jenness >> >> >> ___ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
Tim, On Wed, Sep 9, 2015 at 10:52 AM, Tim Jenness wrote: > > On Sep 9, 2015, at 10:49 , Bill Deegan wrote: > > 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. > > > The scons release notes are very specific: > > > This will be the last release to support Python versions earlier than 2.7, > as we begin to move toward supporting Python 3. > > Which reads to me that 2.6 is being dropped and python 3 is to be > supported. > This doesn't conflict with what I wrote in any way. A guarantee that it will work with 2.6 has been removed. As I said above, if a change breaks 2.6 (in the recent past) and there was an equivalently good way to code it which didn't break 2.6, we'd try to use that. That said, I don't think this came up very often. And as I said above that, shall we say, suggestion is no longer in effect. At some point (undefined as in no hard commitment on the date of a release which will work with 3.x) in the future 3.x will be supported. We've got a fairly big change in default (slots), which should released sometime in the near future. Then we've got another larger functional patch (improved cross language scanners, if it's ready). Also a fix for some issues with versioned shared librareis, and 3.x work should happen thereafter. After that I expect we'll start moving the code to 3.x and 2.7.x compat. Anyone want to volunteer some buildslaves for 3.x? -Bill > > — > Tim Jenness > > > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
> On Sep 9, 2015, at 10:49 , Bill Deegan wrote: > > 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. > The scons release notes are very specific: This will be the last release to support Python versions earlier than 2.7, as we begin to move toward supporting Python 3. Which reads to me that 2.6 is being dropped and python 3 is to be supported. — Tim Jenness ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 difference WRT 3.x compatability in any given version? -Bill Co-Manager, SCons Project On Wed, Sep 9, 2015 at 10:21 AM, Tim Jenness wrote: > > > 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 2.7, but is there a base bugfix version? > > This matters as it determines how much of Python 3 can be assumed. > > > > I have no visibility into how the python3 scons branch is keeping up with > current releases. > > > Are we going to drop the requirement to run on Python 2.6? Currently > > 2.7 is the base but people keep making changes to have things run on > > 2.6. > > > > The last few release notes have been insistently stating that pythons > older than 2.7 will no longer be supported by scons so this is a bit > confusing if scons is still trying to support 2.6. > > — > Tim Jenness > ___ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
> 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 2.7, but is there a base bugfix version? > This matters as it determines how much of Python 3 can be assumed. > I have no visibility into how the python3 scons branch is keeping up with current releases. > Are we going to drop the requirement to run on Python 2.6? Currently > 2.7 is the base but people keep making changes to have things run on > 2.6. > The last few release notes have been insistently stating that pythons older than 2.7 will no longer be supported by scons so this is a bit confusing if scons is still trying to support 2.6. — Tim Jenness ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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 Python 3 can be assumed. Are we going to drop the requirement to run on Python 2.6? Currently 2.7 is the base but people keep making changes to have things run on 2.6. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder ___ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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 one or two people working full time to finish the Python 3 port of SCons, and whilst they didn't immediately say "no", but rather "hummm…" the best we can hope for is someone's time for 1 day a week for a period. Given the current development state of SCons I think we should go out actively with a begging bowl trying to find cash resources to hire someone. This would however require the SCons Foundation to be competant to sign contracts and have a bank account. Is this currently the case? Are the controllers of the foundation active? Thanks. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 SCons devs. On Mon, Mar 10, 2014 at 8:15 PM, Gary Oberbrunner wrote: > 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 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 default? >> >> -- >> Russel. >> = >> Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net >> 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk >> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >> >> ___ >> Scons-dev mailing list >> Scons-dev@scons.org >> http://two.pairlist.net/mailman/listinfo/scons-dev > > > > -- > Gary > ___ > Scons-dev mailing list > Scons-dev@scons.org > http://two.pairlist.net/mailman/listinfo/scons-dev -- anatoly t. ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] SCons and Python 3
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 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 default? > > -- > Russel. > = > Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > ___ > Scons-dev mailing list > Scons-dev@scons.org > http://two.pairlist.net/mailman/listinfo/scons-dev -- Gary ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
[Scons-dev] SCons and Python 3
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 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
