date handling: failing tests, chronic causes different behavior about optimist HOT 4 CLOSED

#parse_data_parameter tries to load chronic and if it fail to load, then the Date behavior of Trollop is "normal". Maybe the tests either need to have chronic as a hard dependency, or bypass the tests that would fail if chronic was not available.

Again, i'm not really a big fan of the behavior changing based on existence of another installed gem - in a group environment (e.g. a University), someone may install a gem (chronic) into a "global" Ruby install and then all of the sudden command line tools that use Trollop would start behaving oddly. That would be pretty hard to track down. 😕

from optimist.

I second this. As chronic is optional 6d45d0e test should be passing without it being installed.

I’ve filed separate #86 before I’ve noticed this issue already mentions problem with failing tests.

from optimist.

This is tricky.
We need the gem installed to run the tests.

So it will be tricky to run tests that fail if the gem is not installed

There is the american_date gem that swaps that date order as well.
Many programming languages (and government agencies) have confusion around %m/%d/%y vs %d/%m/%y

from optimist.

@kbrock ic, perhaps an explicit message that tests are failing due to a missing gem would suffice. Trollop 1.2.1 was masked in Gentoo with recent Ruby versions simply because maintainer didn’t investigate deep enough.

from optimist.