In the current form yes. We can use features in pip to get the packages and install them in a directory contained within the src-local area of scons and modify the startup script to add a python path to the packages. This can be zipped up and used to solve this problem. I did something like this for one of my last projects at Intel.
Jason From: Bill Deegan Sent: Saturday, December 26, 2015 9:23 PM To: SCons developer list Subject: Re: [Scons-dev] That was easy… The only question is would this break the scons-local distributions? On Sat, Dec 26, 2015 at 6:13 PM, Jason Kenny <[email protected]> wrote: +1 Sent from my Windows Phone -----Original Message----- From: "Bill Deegan" <[email protected]> Sent: 12/26/2015 7:00 PM To: "SCons developer list" <[email protected]> Subject: Re: [Scons-dev] That was easy… If we change to suggesting pip/easy_install to be the preferred method of installing, then we can include any other packages we need and not have to "Vendorize" them. On Sat, Dec 26, 2015 at 9:19 AM, Russel Winder <[email protected]> wrote: On Fri, 2015-12-25 at 13:15 -0500, Neal Becker wrote: > […] > > I should have said, I don't think we can make installing future a > requirement for using scons. > > In my case, I was using lineprofiler. It does something strange > with > builtins, and the reason lineprofiler mysteriously stopped working > after > future was installed was hard to find. So the consequence of this is that we can only go to a level 1 futurize and then the rest needs to be manually hacked so that there is no future dependency? I suspect this means we will end up rewriting quite a chunk of future, though not the bits needed for Python 2.6. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
