Tim Jenness wrote: > > >> On Dec 25, 2015, at 10:26 , Neal Becker >> <[email protected]> wrote: >> >> Tim Jenness wrote: >>> >>> I’m not really sure what you mean. future package doesn’t have any >>> dependencies as far as I can tell from the requirements.txt in the >>> package. There are some additional dependencies if you need the code to >>> work on python 2.6 but that’s not an issue here. >>> >>> futurize -1 doesn’t inject dependencies into the code base itself. >>> >>> — >> Haven't tried futurize with '-1', but I meant that if you pip install >> future >> it installs many entries into site-packages, in a very intrusive manner. >> If you pip install future, it puts not only future and past into >> site-packages, >> but such goodies as builtins, and many more. The builtins caused me >> conflicts which were very difficult to track down. >> > > builtins is meant to be a no-op on python3. It replaces python2 builtins > with implementations that match the python3 spec (such as returning > iterators instead of lists; and making strings look like python3 unicode). > > — > Tim Jenness
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. _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
