On Mon, Mar 3, 2014 at 2:37 PM, Bill Deegan wrote:
> Other opinions on PEP-8 formatting compliance?
We have bigger fish to fry IMHO.
--
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev
Dirk,
Yes I agree. Low importance task.
-Bill
On Mon, Mar 3, 2014 at 11:52 AM, Dirk Bächle wrote:
> On 03.03.2014 20:37, Bill Deegan wrote:
>
>> Anatoly,
>>
>> This is a bikeshed'ing type discussion.
>> So we'll never agree on this.
>>
>> The project has long had the emacs/vim info in each so
On 03.03.2014 20:37, Bill Deegan wrote:
Anatoly,
This is a bikeshed'ing type discussion.
So we'll never agree on this.
The project has long had the emacs/vim info in each source file, so
there's no reason to change.
That said, some automated checking in buildbot might not be a bad idea.
Thou
Anatoly,
This is a bikeshed'ing type discussion.
So we'll never agree on this.
The project has long had the emacs/vim info in each source file, so there's
no reason to change.
That said, some automated checking in buildbot might not be a bad idea.
Though I'd put money that SCons source code (hav
Isn't pull request reviews are here to make new people aware of coding
standards?
It is better to setup one's editor right for the whole project than to
save editor
settings in each file.
If an editor doesn't follow PEP-8 rules for .py files by default, it
is not Python (and
SCons) compatible. =)
Anatoly,
Have to disagree 100% on this.
That's why there's a proliferation of tools to ensure styles are followed.
-Bill
On Mon, Mar 3, 2014 at 6:37 AM, anatoly techtonik wrote:
> On Sun, Mar 2, 2014 at 9:07 PM, Russel Winder
> wrote:
> > The SCons source files all seem to have Emacs and Vi/V
I'll take a look to see how much work it would be, and then let the group
know.
I see the following as a reasonable way.
Tools query some package for valid path values.
That package can check for:
SCONS_TOOLS_PATH
And/or provide a way for SConsctrucs and site_init.py to set the PATH(s)
-Bill
On
Gary,
I'm fairly certain there was a copyright assignment form I signed at one
point for SCons.
I'll have to check. Could be confusing with other projects.
-Bill
On Mon, Mar 3, 2014 at 10:41 AM, Bill Deegan wrote:
> Anatoly,
>
> Have to disagree 100% on this.
> That's why there's a proliferati
On Mon, 2014-03-03 at 16:50 +, Managan, Rob wrote:
> Not to cause more flaming but to state what actually exists, a while back
> we taught
> Scons to be aware of an OSX way that paths are set. Namely, the files
> /etc/paths and
> all files in /etc/paths.d/ contain one path per line that gets ad
Hi,
/proc doesn't even exist on OSX.
http://superuser.com/questions/631693/where-is-the-proc-folder-on-mac-os-x
2014-03-03 18:10 GMT+01:00 Gary Oberbrunner :
> On Mac I see the three usual handles plus a couple of other numeric
> entries in /dev/fd as directories; I don't understand those but wi
On Mac I see the three usual handles plus a couple of other numeric entries
in /dev/fd as directories; I don't understand those but will take a look.
On Mon, Mar 3, 2014 at 11:57 AM, Tom Tanner (BLOOMBERG/ LONDON) <
ttann...@bloomberg.net> wrote:
> Just been hunting around and apparently it's /d
Just been hunting around and apparently it's /dev/fd (rather than /proc/xxx/fd)
on MacOS, and also apparently /dev/fd will work equally well for linux
(although presumably ls -l /dev/fd will actually produce the handles ls has
passed to it)
If someone who has MacOS could test that and see if it
Hi,
On OSX 10.7.5 I get this:
ls /proc/$$/fd | wc -l
ls: /proc/97956/fd: No such file or directory
0
So it appears that item 2 below is the culprit.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob Managan email managan at llnl.gov
LLNL
Not to cause more flaming but to state what actually exists, a while back
we taught
Scons to be aware of an OSX way that paths are set. Namely, the files
/etc/paths and
all files in /etc/paths.d/ contain one path per line that gets added to
the system path
For finding executables. When X11 gets ins
I think Anatoly's right -- at least we haven't required contributor
assignments from anyone before.
On Mon, Mar 3, 2014 at 9:48 AM, anatoly techtonik wrote:
> On Mon, Mar 3, 2014 at 3:40 PM, Russel Winder
> wrote:
> > On Mon, 2014-03-03 at 06:05 -0500, Gary Oberbrunner wrote:
> >> On Mon, Mar 3
On Mon, Mar 3, 2014 at 3:40 PM, Russel Winder wrote:
> On Mon, 2014-03-03 at 06:05 -0500, Gary Oberbrunner wrote:
>> On Mon, Mar 3, 2014 at 2:24 AM, Russel Winder wrote:
>>
>> > In SCons' case the situation is easy, the assigned or
>> > shared copyright should rest with the SCons Foundation, and
On Sun, Mar 2, 2014 at 9:07 PM, Russel Winder wrote:
> The SCons source files all seem to have Emacs and Vi/Vim data at the
> bottom, but the data seems to just replicate the defaults. I just copy
> and paste for any new files, but is the the right thing to be doing?
I think this source pollution
On Mon, 2014-03-03 at 06:04 -0500, Gary Oberbrunner wrote:
> On Mon, Mar 3, 2014 at 2:35 AM, Russel Winder wrote:
>
> > Having an entry 'test_base_path = '...' in a ~/.scons/settings.py or
> > something similar would work fine for me. This only alters the behaviour
> > for tests, not for normal e
On Mon, 2014-03-03 at 06:05 -0500, Gary Oberbrunner wrote:
> On Mon, Mar 3, 2014 at 2:24 AM, Russel Winder wrote:
>
> > In SCons' case the situation is easy, the assigned or
> > shared copyright should rest with the SCons Foundation, and it should be
> > the foundation that is the published copyr
On Mon, 2014-03-03 at 09:19 +, Tom Tanner (BLOOMBERG/ LONDON) wrote:
> On the OSX one, it looks like you don't have SWIG and RANLIB installed
> and it's not recognising that it hasn't. I seem to remember having to
> install a lot of software on my linux (Ubuntu) box in order to get the
> tests
On Mon, 2014-03-03 at 09:19 +, Tom Tanner (BLOOMBERG/ LONDON) wrote:
[…]
> I don't have access to an OSX system so I can't really tell, though if it
> (os.name) returns 'posix' that should work.
Python 2.7.6 on OSX Mavericks pulled in via MacPorts definitely return
'posix' for os.name, just a
On Mon, Mar 3, 2014 at 2:35 AM, Russel Winder wrote:
> Having an entry 'test_base_path = '...' in a ~/.scons/settings.py or
> something similar would work fine for me. This only alters the behaviour
> for tests, not for normal execution.
>
+1 -- though I'd suggest it be called test_settings.py a
On Mon, Mar 3, 2014 at 2:24 AM, Russel Winder wrote:
> In SCons' case the situation is easy, the assigned or
> shared copyright should rest with the SCons Foundation, and it should be
> the foundation that is the published copyright owner.
>
Yes, this is correct.
--
Gary
__
On the OSX one, it looks like you don't have SWIG and RANLIB installed and it's
not recognising that it hasn't. I seem to remember having to install a lot of
software on my linux (Ubuntu) box in order to get the tests to run clean. If
that's the case, I'd imagine it's a bug really.
The leaky-ha
24 matches
Mail list logo
