Tests depend on specific `TZ` setting

Try

TZ=UTC python setup.py test

This should cause timestamp-parsing-related test failures.

I suppose that the timestamp parser relies on the current TZ environment setting being the same as the one used for generating the timestamp, which might not be the case for the pre-recorded test input. I had to explicitly run

TZ=America/Los_Angeles python setup.py test

to make the tests succeed.

IMHO, the test script should take care of setting the expected timezone.

[kellyjonbrazil]

Actually, I think I’m just going to .upper() the period (‘AM’/‘PM’) text so it’s always consistent across systems.

[kellyjonbrazil]

Hi @chocolateboy - thanks for reporting this. This looks like a separate issue around the capitalization of the AM/PM period in the jc output. On my system it looks like AM/PM should be capitalized, though it looks like it is lowercase on your system.

What python version is installed on the system?

According to this (https://stackoverflow.com/questions/38863210/how-to-make-pythons-datetime-object-show-am-and-pm-in-lowercase#:~:text=In the en_US locale%2C AM,You can use locale.) it looks like the capitalization of AM/PM can depend on the Locale setting. Maybe I can set the Locale for the tests to C so they don’t fail.