diff options
author | bors-servo <lbergstrom+bors@mozilla.com> | 2017-04-10 17:53:37 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-04-10 17:53:37 -0500 |
commit | ca3cd64d6b1999292d634bfa237c2705e6d575c1 (patch) | |
tree | e93d8c06397c85307fa7a4ad79f4e0a03bdb538a /components/layout/text.rs | |
parent | 4013e9d7a0be666343ef9d806408af5c0a852d91 (diff) | |
parent | c8e43958add3e04fc3efe510967d50b85425ea21 (diff) | |
download | servo-ca3cd64d6b1999292d634bfa237c2705e6d575c1.tar.gz servo-ca3cd64d6b1999292d634bfa237c2705e6d575c1.zip |
Auto merge of #16338 - Wafflespeanut:byte, r=jdm
Disable bytecode generation in mach
Recently, [@]froydnj had some trouble with `mach`, and after half an hour of struggle, a simple `git clean` and `git reset --hard` seemed to fix the issue. Apparently, sometimes (though I'm not sure when, and I don't even have a convincing argument), the changes to `mach` scripts don't really seem to reflect on the related bytecode files (when it absolutely should've!).
Having bytecode files is just a matter of optimization (i.e., we don't have to compile the scripts again), but when it comes to our simple build system, "not having them" doesn't add a great overhead. So, we could just disable their creation to avoid such issues in the future.
Existing users can do `find ./python -name '*.pyc' -delete` for a cleanup (and maybe remove the `python/_virtualenv` directory too, though not necessary)
<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/16338)
<!-- Reviewable:end -->
Diffstat (limited to 'components/layout/text.rs')
0 files changed, 0 insertions, 0 deletions