<div dir="ltr">@Chris: yeah, like I said in my original post, that's the ideal approach. I've worked with this technique using <a href="http://coveralls.io">coveralls.io</a> before and I really like it. Problem is I'm currently running on some corporate build infrastructure (not my call) that's really slow to change and I won't be able to get that quickly enough. Was looking for some other ideas as a temporary work around to buy some time.<div><br></div><div>André</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 2, 2016 at 7:35 AM, Ned Batchelder <span dir="ltr"><<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>This is definitely the most common approach. Some people want to
see that they have complete coverage on each platform
independently, though I have never tried that myself. André
indicated he could not use combine for whatever reason, not sure
why.</p><span class="HOEnZb"><font color="#888888">
<p>--Ned.<br>
</p></font></span><div><div class="h5">
<br>
<div>On 8/2/16 6:27 AM, Chris Withers wrote:<br>
</div>
<blockquote type="cite">
<p>When I hit this, I just ran the tests on the various platforms
and used "coverage conbine" to get them into one place before
making assertions.</p>
<p>cheers,</p>
<p>Chris<br>
</p>
<br>
<div>On 27/07/2016 18:56, André Caron
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Neat! Looks like a winner, at least until I have
more than 2 platforms (this mechanism being based on
exclusion, I have to "negate" the platform, which may yield
multiple results).
<div><br>
</div>
<div>André</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 27, 2016 at 9:54 AM, Ned
Batchelder <span dir="ltr"><<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>You can use environment variables in the .coveragerc
file, so you can create a pattern for pragmas that
uses environmental data. For example: <a href="https://github.com/habnabit/ebb-lint/blob/master/.coveragerc" target="_blank">https://github.com/habnabit/ebb-lint/blob/master/.coveragerc</a>
:<br>
</p>
<blockquote>
<p><tt>[report]</tt><tt><br>
</tt><tt>exclude_lines =</tt><tt><br>
</tt><tt> pragma: no ${TOX_ENVNAME}</tt><tt><br>
</tt><tt> pragma: no ?cover</tt><br>
</p>
</blockquote>
<p>--Ned.<br>
</p>
<div>
<div>
<p><br>
</p>
<p> </p>
<div>On 7/26/16 6:33 PM, André Caron wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">Hi all,
<div><br>
</div>
<div>I have some code base that has
platform-specific code, mostly related to how
to handle SIGINT and CTRL-C for which I like
to use `coverage report --fail-under=100`.
Problem is that some code only runs on one OS,
so coverage is always partial in those cases
and it's not so straightforward.</div>
<div><br>
</div>
<div>I've used Coveralls for some open source
projects and their solution AFAICT seems to be
to collect the `.coverage` files in a central
location and then combine the coverage files,
after which you can run the actual reporting.</div>
<div><br>
</div>
<div>However, I'm not in a position to use
Coveralls for this project and integrating a
distributed coverage combine is not viable in
the short/medium term.</div>
<div><br>
</div>
<div>I'm looking for suggestions on a quick and
dirty way to solve this.</div>
<div><br>
</div>
<div>One thing I thought of was using coverage's
`exclude_lines` option [1] with a platform
specific token to get this:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div>if sys.platform == 'win32': # pragma:
cover win32</div>
</blockquote>
<div><br>
</div>
<div>I guess this works, but it requires that I
have a platform-specific configuration file
(e.g. via duplicatation or generation from a
template).</div>
<div><br>
</div>
<div>Anybody have any better ideas?</div>
<div><br>
Thanks,</div>
<div><br>
</div>
<div>André</div>
<div><br>
</div>
<div>[1]: <a href="https://coverage.readthedocs.io/en/coverage-4.1/excluding.html#advanced-exclusion" target="_blank">https://coverage.readthedocs.io/en/coverage-4.1/excluding.html#advanced-exclusion</a></div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
testing-in-python mailing list
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" rel="noreferrer" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
testing-in-python mailing list
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>