Team Chat Logs

February 13, 2010

2010 1
Mo Tu We Th Fr Sa Su
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
<< <   > >>

[04:22:25.218031]<fatbrain>I'm trying to use coverage (http://nedbatchelder.com/code/coverage/), am I correct to "assert" that Bitten doesn't support that tool "out-of-the-box" as it does with "figleaf"?
[04:22:57.964327]<osimons>fatbrain: no, not correct - hang on
[04:23:09.637868]*fatbrain is hanging on.
[04:23:38.247383]<fatbrain>(adding: problem I've had is that coverage doesn't produce any coverdir output :S)
[04:24:59.528342]<osimons>oh dear.
[04:25:12.181954]<fatbrain>heh
[04:26:01.186304]<osimons>it is here: http://bitten.edgewall.org/browser/trunk/bitten/build/pythontools.py#L173
[04:26:25.604903]<osimons>but that whole command seems to have dropped out of the docs somehow: http://bitten.edgewall.org/wiki/Documentation/commands.html#python-tools
[04:26:31.695073]*osimons checks...
[04:27:14.043263]<fatbrain>checking.
[04:30:20.497641]*fatbrain is no more, trying the coverage.py configuration.
[04:33:39.148395]<fatbrain>osimons: Thanks, worked like a charm.
[04:33:47.264979]<fatbrain>(been looking for that for 4 hours :D)
[04:33:54.891390]<osimons>fatbrain: heh. sorry :-)
[04:33:57.051308]<fatbrain>(while doing other stuff of course ;))
[04:34:02.696269]<fatbrain>not your fault ;)
[04:34:17.917248]<osimons>could you paste your step sample (edited) and i'll put it into the example of the docs?
[04:34:45.588284]<osimons>i don't have a tested recipe for that command in any of my examples, so be nice to get something that is verified to work :-)
[04:44:43.174790]<osimons>fatbrain: you can really just take the figleaf example, and change it to use "--coverage-method coverage" instead
[04:44:54.876418]<osimons>me thinks - at least that is what the docs will say :-9
[04:50:37.480109]<fatbrain>yeah, think that was what I did :)
[04:51:29.837456]<fatbrain>and change the <python:figleaf to <python:coverage and removed the coverdir attribute.
[05:00:52.246280]<osimons>fatbrain: "removed"? "added" you mean as python:coverage supports coverdir but not figleaf, right?
[05:01:56.154614]<osimons>anyway, here is the example i'm now adding to docs: http://paste.pocoo.org/show/177449/
[05:06:19.131325]<osimons>...and committed: http://bitten.edgewall.org/changeset/811
[05:06:23.049548]<osimons>thanks, fatbrain.
[05:08:50.523431]<osimons>yay, the [[include]] macro: http://bitten.edgewall.org/wiki/Documentation/commands.html#python-coverage
[10:40:09.516721]<fatbrain>Hrm, can I somehow get information about translations into bitten somehow? i.e. list of all langauges with untranslated / fuzzy etc?
[11:12:07.643348]<osimons>fatbrain: as plain-text log at least, then sure. run a 'find' to locate your .po files and for instance run msgfmt --check --statistics path/to/messages.po
[11:12:40.645767]<osimons>there is no structured reporting support for languages - although that would be useful enough one day
[11:12:41.794701]<fatbrain>osimons: I was hopeing for some more elaborate output than a plain-text log.
[11:12:56.736693]<fatbrain>yes, I may hack something together.
[11:14:27.670604]<osimons>define a report format for 'locale' http://bitten.edgewall.org/wiki/ReportFormats - and then make report summarizer/grapher to parse and present the info - like for instance this example for 'lint' reports: http://bitten.edgewall.org/browser/trunk/bitten/report/lint.py
[11:15:17.906250]<fatbrain>will do (after valentines day)
[11:15:39.788197]<osimons>i'll happily add such extensions to Bitten :-)
[11:16:02.443843]<fatbrain>goodie
[11:37:16.370401]<osimons>localization is a good candidate for structured reporting, i guess