Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upPackage tidy #10590
Package tidy #10590
Conversation
highfive
commented
Apr 13, 2016
|
Thanks for the pull request, and welcome! The Servo team is excited to review your changes, and you should hear from @pcwalton (or someone else) soon. |
highfive
commented
Apr 13, 2016
|
Heads up! This PR modifies the following files:
|
|
Do we know whether anyone's actually running the Tidy selftests through the mach-centric |
|
I'm not entirely clear what you're asking; TravisCI is running |
|
Due to servo_tidy cannot be found on PyPI now, the test will failed. $ cd <SERVO>
$ rm -rf ./python/_virtualenv/
$ ./mach help
$ # for init the _virtualenv, it will show error msg: Could not find a version that satisfies the requirement servo-tidy==0.0.1
$
$ source ./python/_virtualenv/bin/activate
$ pip install -e python/tidy/
$ # install servo_tidy from local
$ deactivate
$
$ ./mach test-tidy --self-test |
#861 (comment) "I think the most important concern is that it's possible to modify tidy.py and see how those changes affect ./mach test-tidy with the fewest possible intermediate steps." - jdm This takes publishing complexity away from the contributor when testing changes and makes it an infra problem instead, where it's much easier to automate & saner to manage pypi credentials
| @@ -13,3 +13,5 @@ pyflakes == 0.8.0 | |||
|
|
|||
| # For test-webidl | |||
| ply == 3.8 | |||
|
|
|||
| -e python/tidy | |||
This comment has been minimized.
This comment has been minimized.
askeing
Apr 14, 2016
Contributor
Cool!
I never knew we can use -e foo/bar in requiremnets.txt before.
It's really helpful to avoid the publish problems, and make testing easier :)
… tidy check - fix the issue of '$ ./mach test-tidy --no-progress'
|
All checks have passed :) |
|
@askeing we'll only need to rebase if the master branch develops a merge conflict with these changes before the PR lands. Since there've been no major changes in |
|
Reviewed 1 of 43 files at r1, 1 of 29 files at r2, 10 of 42 files at r4, 28 of 33 files at r5, 2 of 3 files at r6, 1 of 1 files at r7, 2 of 2 files at r8. Comments from Reviewable |
|
@bors-servo r+ |
|
|
Package tidy This fixes #861. @askeing, I've copied your work from https://github.com/askeing/servo_tidy and attributed the commit to you. My commit in this PR is Git housekeeping to preserve `tidy`'s history. If you'd like to make additional changes, I've given you and @shinglyu push access to my fork of Servo. Apologies if this is already familiar, but the workflow for pushing to my branch is: ``` $ git remote add edunham git@github.com:edunham/servo.git $ git checkout -b package-tidy $ git pull edunham package-tidy $ git push edunham package-tidy ``` Once this lands, I'll look at how to publish it to PyPI and automate that process. Please don't merge this yet; we still need to discuss how the change should work around https://github.com/servo/servo/blob/master/python/servo/testing_commands.py#L33 , as I've yet to figure out how to get the egg to actually expose its tests. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10590) <!-- Reviewable:end -->
|
|
Docs and cleanup after moving tidy Missed a couple things in #10590 `licenseck.py` was moved into `tidy/servo_tidy/licenseck.py` by the prior PR r? @larsbergstrom (sorry for PR spamming today) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10635) <!-- Reviewable:end -->
Docs and cleanup after moving tidy Missed a couple things in #10590 `licenseck.py` was moved into `tidy/servo_tidy/licenseck.py` by the prior PR r? @larsbergstrom (sorry for PR spamming today) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10635) <!-- Reviewable:end -->
Docs and cleanup after moving tidy Missed a couple things in #10590 `licenseck.py` was moved into `tidy/servo_tidy/licenseck.py` by the prior PR r? @larsbergstrom (sorry for PR spamming today) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10635) <!-- Reviewable:end -->
…m:tidy-cleanup); r=larsbergstrom Missed a couple things in servo/servo#10590 `licenseck.py` was moved into `tidy/servo_tidy/licenseck.py` by the prior PR r? larsbergstrom (sorry for PR spamming today) Source-Repo: https://github.com/servo/servo Source-Revision: 9d23d7c0d98e24995243487b55abbf2acd1ec354 UltraBlame original commit: 5b7a48485a8a5825e6041fccfbf7f0e69be725a3
…m:tidy-cleanup); r=larsbergstrom Missed a couple things in servo/servo#10590 `licenseck.py` was moved into `tidy/servo_tidy/licenseck.py` by the prior PR r? larsbergstrom (sorry for PR spamming today) Source-Repo: https://github.com/servo/servo Source-Revision: 9d23d7c0d98e24995243487b55abbf2acd1ec354 UltraBlame original commit: 5b7a48485a8a5825e6041fccfbf7f0e69be725a3
…m:tidy-cleanup); r=larsbergstrom Missed a couple things in servo/servo#10590 `licenseck.py` was moved into `tidy/servo_tidy/licenseck.py` by the prior PR r? larsbergstrom (sorry for PR spamming today) Source-Repo: https://github.com/servo/servo Source-Revision: 9d23d7c0d98e24995243487b55abbf2acd1ec354 UltraBlame original commit: 5b7a48485a8a5825e6041fccfbf7f0e69be725a3
edunham commentedApr 13, 2016
This fixes #861.
@askeing, I've copied your work from https://github.com/askeing/servo_tidy and attributed the commit to you. My commit in this PR is Git housekeeping to preserve
tidy's history. If you'd like to make additional changes, I've given you and @shinglyu push access to my fork of Servo. Apologies if this is already familiar, but the workflow for pushing to my branch is:Once this lands, I'll look at how to publish it to PyPI and automate that process.
Please don't merge this yet; we still need to discuss how the change should work around https://github.com/servo/servo/blob/master/python/servo/testing_commands.py#L33 , as I've yet to figure out how to get the egg to actually expose its tests.
This change is