On Mon, Mar 13, 2017 at 10:35:45AM +0000, Matthew Seaman wrote: > On 2017/03/13 04:27, The Doctor wrote: > > back to the question: Why is python still choking > > > > even after a port reinstall? > > > > Did you change the default version of python in your make.conf recently? > Is it possible you have a mixture packages of (or depending on) > different versions of python? > > I suspect that the problem is down to your build environment -- > something else you have installed is getting caught up in the build > process when it shouldn't be. The ports are meant to be resistant to > such things, but they can't make any absolute guarrantees. Plus now the > tendency is to use clean-room builds via poudriere or similar which are > intrinsically proof against such things. > > Cheers, > > Matthew > >
I wonder if I should just abandon python2 for either python35 or python34? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
