Displaying timezone information in HTML report

[xyb]

No description provided.

[nedbat]

Thanks for doing this, and sorry for my silence.

I'm curious why the timezone is important on the report?

I have some concerns about the code. On my Mac, on 2.7, the timezone is shown as "+2000", but on 3.7, it's "-0400". I'm not that comfortable with maintaining the fallback code for format_local_datetime. How would you feel about displaying the timezone only for Python versions that can do it natively (3.6+)?

[codecov-commenter]

Codecov Report

Merging #960 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #960   +/-   ##
=======================================
  Coverage   94.03%   94.04%           
=======================================
  Files          86       86           
  Lines       12102    12182   +80     
  Branches     1211     1224   +13     
=======================================
+ Hits        11380    11456   +76     
- Misses        588      590    +2     
- Partials      134      136    +2     

Impacted Files	Coverage Δ
coverage/backward.py	95.74% <100.00%> (+0.18%)	⬆️
coverage/html.py	100.00% <100.00%> (ø)
tests/test_html.py	99.24% <100.00%> (-0.38%)	⬇️
coverage/summary.py	88.07% <0.00%> (-4.09%)	⬇️
tests/test_xml.py	100.00% <0.00%> (ø)
tests/test_arcs.py	100.00% <0.00%> (ø)
tests/test_json.py	100.00% <0.00%> (ø)
tests/test_config.py	100.00% <0.00%> (ø)
coverage/xmlreport.py	100.00% <0.00%> (ø)
... and 9 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f318f93...d66983d. Read the comment docs.

[xyb]

I'm curious why the timezone is important on the report?

I have multiple CI servers that have different time zones, so I would like to know the exact time of the test report.

How would you feel about displaying the timezone only for Python versions that can do it natively (3.6+)?

Sounds good. The backward compatible code is ugly, let's get rid of it :)

[nedbat]

Thanks! I merged it, and had to fix the test (sometimes time zones are -XXXX instead of +XXXX).

[nedbat]

This is available in coverage 5.2.1.