[issue17465] Gut devinabox

2013-03-21 Thread Brett Cannon
Brett Cannon added the comment: OK, rewrite is finished in changeset 2c20681befa8 . -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker __

[issue17465] Gut devinabox

2013-03-20 Thread Brett Cannon
Brett Cannon added the comment: OK, so I think supporting builds, runs, and reports is fine to start, but trying to get the setup step for Distribute working would be a bonus feature if we wanted to make this something we ask people to use on their own w/o guidance. -- ___

[issue17465] Gut devinabox

2013-03-19 Thread R. David Murray
R. David Murray added the comment: Coverage takes a long time to run. So I think what is needed is running it once to build the full report (I then shared that on a local http server), and a script the sprinters can run to re-run it just against the module they are writing tests for. Which i

[issue17465] Gut devinabox

2013-03-19 Thread Brett Cannon
Brett Cannon added the comment: One piece of feedback I could stand to get from people who have used a devinabox at a sprint is how often a certain step is repeated in terms of coverage.py (since it's the most complicated one). Which one happens the most? 1. Checkout, setup, build, and cover o

[issue17465] Gut devinabox

2013-03-19 Thread Brett Cannon
Brett Cannon added the comment: Here is the overall plan. 1. A README for core devs leading a sprint to make sure they remember to have the right repositories cloned, files downloaded, and docs built; stuff they already know how to do and thus don't need a tool to do for them which constantly

[issue17465] Gut devinabox

2013-03-19 Thread anatoly techtonik
anatoly techtonik added the comment: Given some tweaks, it can become an attracting entrypoint into Python core development - http://shelr.tv/records/5148841296608075f849 -- nosy: +techtonik ___ Python tracker

[issue17465] Gut devinabox

2013-03-19 Thread Nick Coghlan
Nick Coghlan added the comment: When I used it for PyCon AU, it did require tweaking, but only for some of the steps. It was still handy to have it automated, I just think we need to set the expectation that we'll need to tweak the scripts every time we use it for a new conference. It would a

[issue17465] Gut devinabox

2013-03-18 Thread R. David Murray
R. David Murray added the comment: A script to do all the steps is what devinabox currently is, but it is rather fagile. As far as I know (Brett would know for sure) it has never worked without tweaking from one Core Sprint to the next. -- ___ Pyth

[issue17465] Gut devinabox

2013-03-18 Thread Ezio Melotti
Ezio Melotti added the comment: > What devinabox should become instead is a README listing what people > should checkout/download and build. Isn't this already covered in the devguide? If it's not I think it should be added there rather than on a README. I'm also not sure what the current de

[issue17465] Gut devinabox

2013-03-18 Thread Brett Cannon
New submission from Brett Cannon: While devinabox was originally designed such that anyone running a core dev sprint could have an easy way to grab everything, it has turned out only core devs end up using it. That makes having a script to do checkouts, builds, etc. is overkill. What devinabo