Skip to content

Commit 43b8c00

Browse files
committed
Add --epoch to base tutorial
1 parent cca0c22 commit 43b8c00

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

docs/images/types.png

-22 Bytes
Loading

docs/tutorial_basic.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -433,8 +433,9 @@ Date Handling
433433
The other important switches are those used in the detection of dates encoded
434434
as numbers: :option:`structa --min-timestamp` and :option:`structa
435435
--max-timestamp`. When dates are encoded as (potentially fractional)
436-
day-offsets from the UNIX epoch (the 1st January, 1970), how does structa
437-
determine that it's looking at a set of dates rather than a set of numbers?
436+
day-offsets from some :option:`structa --epoch` (which defaults to the UNIX
437+
epoch, i.e. the 1st January, 1970), how does structa determine that it's
438+
looking at a set of dates rather than a set of numbers?
438439

439440
In a typical set of (arbitrary) numbers, it's quite normal to find "0" or "1"
440441
commonly represented, or for the set of numbers to span over a large range

0 commit comments

Comments
 (0)