[GRASS-dev] dateutil dependency killing GRASS 7

[Moritz Lennert]

On 17/10/12 22:20, Glynn Clements wrote:
>
> Moritz Lennert wrote:
>
>>> sorry to introduce something painful as a python-dateutil dependency.
>>> My fault. I should have discussed this on the list indeed.
>>>
>>> I have completely removed the dateutil dependency from the temporal
>>> GIS in r53435. For now
>>> only two types of calendar time stings are supported for parsing.
>>
>> Do you really have to remove it completely ? Can't you check for its
>> presence and if not present fall back on the basic date version ? And
>> put a hint in the manuals about its installation being strongly
>> recommended ?
>
> Then it would become a /de facto/ mandatory dependency.
>

Is it illegitimate to propose basic functionality, thus allowing the 
user to use the modules, but forcing them to be more rigorous about date 
format, etc, but offer the user a way to more "comfort" by installing an 
additional dependency ?

If the use of dateutil creates a whole lot of new, additional 
functionality (beyond increase in comfort) which you don't get without, 
then I agree with you.

Moritz