TimestampConverter converts timedelta objects as datetime.now(UTC) + timedelta

[fubuloubu]

Not sure if I like that this is the case, or at least I ran into an issue where I expected that putting a timedelta object in the deployment params of a contract that expected a timedelta arg ended up making a quite large timedelta unexpectedly

ape/src/ape/managers/converters.py

Line 229 in 13ea952

return int((datetime.now(timezone.utc) + value).timestamp())

Should this converter instead convert timedelta as td.total_seconds(), and then suggest in the docs to do datetime + timedelta for those scenarios where you want it to produce a specific timestamp and not a delta? e.g.

tx = contract.method(..., chain.pending_timestamp + timedelta(hours=1), ...)

[linear]

APE-1831 TimestampConverter converts `timedelta` objects as `datetime.now(UTC) + timedelta`