Import module without importing there SCons manually?

[dustdfg]

Hello! When you run scons your SConstruct file doesn't need to explicitly load all the SCons modules. The same is with all other files called through SConscript but if I import another module I need to explicitly import SCons parts which I need.

Is there any function like Import("module")?
(I know Import name is already occupied just an example). I know there is Export and Import which allows to pass values between files called with SConscript but I need to import everything from there. I want to replace a import module to Import("module") and do then module.my_func() like it was just normal module loading. Is there something like it? Or do you have any ideas how to do it in another way?

[bdbaddog]

If you look in the manpage, you'll see the following:

Builder methods that can be called without an explicit environment (indicated in the listing of builders below without a leading env.) may be called from custom Python modules that you import into an SConscript file by adding the following to the Python module:

from SCons.Script import *

It's also mentioned in the user guide here: https://scons.org/doc/production/HTML/scons-user.html#id1462

[bdbaddog]

No such thing. And we honeslty won't implement.
That's what site_scons/site_init.py is for.
Anything there is in scope of the SConscripts..
I think that's likely what you're shooting for?

Otherwise if not referenced in site_scons/site_init.py, import xyz will look in site_scons..

[dustdfg]

Many people (which I asked) has opinion about SCons: "It doesn't force you to do almost anything. You can anytime do a workaround and do thing by yourself... Not using builders and etc... But if you want to migrate from not very SConsish codebash to the one which uses SCons in more correct way you can need something like it... I think it is unnecessary for a fully SConsish codebase but for the one which does a migrations it can be a handful thing

[dustdfg]

But do you at least know how to return everything?

[bdbaddog]

just set a package variable and then you can reference it.

import mystuff # This would be site_scons/mystuf.py

x=mystuff.some_stored_value

mystuff.py

some_stored_value="Happy Wednesday"

Yes. You can do whatver you want with SCons. Somethings will not be wise, will be fragile, and hard to track down problems with.

If you go the most mainstream usage (as with any tool), there's likely to be more information,testing, and help available.

[mwichmann]

"Everything" is a big word, but is you want to use the Import/Export mechanism, put everything you want to share in a container, and just export that one name. In fact, the fairly obvious container is... a construction environment.

[mwichmann]

Tool modules have funny importing under the covers, if their particular approach happens to fit your use case, you might be able to make use of a tool.