On Thursday, July 3, 2014 3:31:18 PM UTC-4, William wrote: > > 1. Building in place saves disk space. It saves a *lot* of disk > space,
$ du -sh src/build/lib.linux-x86_64-2.7 344M src/build/lib.linux-x86_64-2.7 Here is a nickel, kid. Go and buy yourself some more disk space ;-) 2. Building in place reduces *confusion*. I can't tell you how > many times I've seen people loose work, get confused, etc., because > they type foo??, see the filename, edit that file (in > local/lib/python/site-packages!), only to find it gets overwritten > later. First of all, I'm confused about what "build in place" is supposed to mean. I thought its about getting rid of src/build/lib.ARCH, which should never have been under src/. But you still need to install files from src/sage/... to local/lib/python/site_packages. Anything else would be utterly confusing. Its perhaps an easy beginner mistake to edit files in the install tree instead of the source tree, but its also easily explained. However, once you start mixing up that clear boundary there is no way of communicating which file needs to be edited. We don't just have python code, there are also scripts and ext code, not to mention third-party packages. And even if one could somehow communicate our design decisions, it would be a totally different convention from everybody else so we'd just be teaching bad practices to the community. Not to mention that it would bring us even further away from the goal of being packageable by distributions. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
