[Scons-users] Tool specification `exists()` not called?

[Márcio Faustino]

On Thu, Oct 10, 2013 at 1:31 PM, Marc Joliet <marcec at gmx.de> wrote:


> Am Wed, 09 Oct 2013 22:09:24 +0200

> schrieb Dirk Bächle <tshortik at gmx.de>:

>

> > On 09.10.2013 21:05, Márcio Faustino wrote:

> > > Hi Dirk,

> > >

> > > I read it online at

> > > <http://www.scons.org/doc/production/HTML/scons-man.html#lbAG>, in the

> > > paragraph starting with "This looks for a tool specification in".

> > >

> >

> > Although this paragraph doesn't state explicitly that the exists()

> > method gets called (nit-picking, I know ;) ), I can understand how it

> > may be misleading...

>

> I had the same confusion, so perhaps that part of the documentation should

> be

> rephrased sometime.

>


Actually I just noticed that although it doesn't get called, SCons still
checks the module defines an "exists". If I remove it:

scons: Reading SConscript files ...
AttributeError: 'module' object has no attribute 'exists':
  File "C:\Users\marcio\Dropbox\Projects\argf\SConstruct", line 9:
    'default', 'find', 'pep8', 'pylint', 'pyunit', 'travis-lint',
'virtualenv'])
  File
"c:\python27\lib\site-packages\scons-2.3.0-py2.7.egg\scons-2.3.0\SCons\Environment.py",
line 1002:
    apply_tools(self, tools, toolpath)
  File
"c:\python27\lib\site-packages\scons-2.3.0-py2.7.egg\scons-2.3.0\SCons\Environment.py",
line 106:
    env.Tool(tool)
  File
"c:\python27\lib\site-packages\scons-2.3.0-py2.7.egg\scons-2.3.0\SCons\Environment.py",
line 1785:
    tool = SCons.Tool.Tool(tool, toolpath, **kw)
  File
"c:\python27\lib\site-packages\scons-2.3.0-py2.7.egg\scons-2.3.0\SCons\Tool\__init__.py",
line 99:
    self.exists = module.exists

-- 
Márcio Faustino
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://four.pairlist.net/pipermail/scons-users/attachments/20131010/2a2f8afc/attachment.html