Posted
over 11 years
ago
by
TAKAHIRO Kitahara
use json.loads and support utf-8 .hgtimestamp
.hgtimestamp
TimestampMod.py
|
Posted
over 11 years
ago
by
Nathan Durnan
Wrap long lines and declarations - attempting to adhere to 80-character limit.
.hgtimestamp
(1 lines added, 1 lines removed)
TimestampMod.py
(248 lines added, 83 lines removed)
|
Posted
over 11 years
ago
by
Nathan Durnan
Wrap long lines and declarations - attempting to adhere to 80-character limit.
.hgtimestamp
TimestampMod.py
|
Posted
over 11 years
ago
by
Nathan Durnan
Update README to include BBI#38 fix details.
(and prepare for 0.2.6 release)
.hgtimestamp
(1 lines added, 1 lines removed)
README.md
(3 lines added, 1 lines removed)
|
Posted
over 11 years
ago
by
Nathan Durnan
Merge with BBI#38 - JSON File with No Timestamps
.hgtimestamp
(3 lines added, 2 lines removed)
Tests/BBI38_EmptyUpdate_Test.bat
(61 lines
|
Posted
over 11 years
ago
by
Nathan Durnan
Close BitBucket Issue #38 - JSON File with No Timestamps
|
Posted
over 11 years
ago
by
Nathan Durnan
Check for no entries in FileData section before testing for errors.
See Issue#38 at BitBucket.
If there are no entries in the FileData section,
then both {{{myWarnCount}}} and {{{len(myData['FileData'])}}}}
would be zero. This is not an error
|
Posted
over 11 years
ago
by
Nathan Durnan
Create test-script for issue.
Creates a new repository, adds a file, then removes it.
Check by updating to Rev-0 (with file) and Rev-1 (without file).
Update to Rev-1 should not trigger an error message or "open-as-CSV".
|
Posted
over 11 years
ago
by
Nathan Durnan
BitBucket Issue #38 - The _read_TimestampJSONRecords function fails and
returns an error when updating to a revision that has no timestamp data recorded.
.hgtimestamp
(1 lines added, 1 lines removed)
|
Posted
over 11 years
ago
by
Nathan Durnan
Update README to include BBI#36 fix details.
(and prepare for 0.2.6 release)
.hgtimestamp
(1 lines added, 1 lines removed)
README.md
(3 lines added, 1 lines removed)
|