Hi, If SCons should move to using pip to be installed, I do hope there would still be as well a simple archive delivery. We try to keep our servers with as little installed softwares/packages as possible, and adding the need to take care of having a working pip on every linux/aix/solaris/windows server would be an additional hassle. Also, I suppose pip would make life harder for projects that need to compile on servers with no internet access.
> Le 27 déc. 2015 à 18:02, Jason Kenny <dragon...@live.com> a écrit : > > 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 <mailto:b...@baddogconsulting.com> > Sent: Saturday, December 26, 2015 9:23 PM > To: SCons developer list <mailto:scons-dev@scons.org> > 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 <dragon...@live.com > <mailto:dragon...@live.com>> wrote: > +1 > > Sent from my Windows Phone > > -----Original Message----- > From: "Bill Deegan" <b...@baddogconsulting.com > <mailto:b...@baddogconsulting.com>> > Sent: 12/26/2015 7:00 PM > To: "SCons developer list" <scons-dev@scons.org <mailto:scons-dev@scons.org>> > 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 <rus...@winder.org.uk > <mailto:rus...@winder.org.uk>> 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:russel.win...@ekiga.net > <mailto:sip%3arussel.win...@ekiga.net> > 41 Buckmaster Road m: +44 7770 465 077 <tel:%2B44%207770%20465%20077> > xmpp: rus...@winder.org.uk <mailto:rus...@winder.org.uk> > London SW11 1EN, UK w: www.russel.org.uk <http://www.russel.org.uk/> > skype: russel_winder > > > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org <mailto:Scons-dev@scons.org> > https://pairlist2.pair.net/mailman/listinfo/scons-dev > <https://pairlist2.pair.net/mailman/listinfo/scons-dev> > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org <mailto:Scons-dev@scons.org> > https://pairlist2.pair.net/mailman/listinfo/scons-dev > <https://pairlist2.pair.net/mailman/listinfo/scons-dev> > > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org <mailto:Scons-dev@scons.org> > https://pairlist2.pair.net/mailman/listinfo/scons-dev > <https://pairlist2.pair.net/mailman/listinfo/scons-dev>
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
