Last modified: 2013-10-09 06:22:18 UTC
Timestamp has been changed since 27th september and does not return mw timestamp as yyyymmddhhmmss but 'yyyy-mm-ddThh:mm:ssZ' which blocks several scripts. Getting 12 pages via API from wikipedia:de... Building wiki table... Traceback (most recent call last): File "C:\pwb\compat\dup.py", line 918, in <module> main() File "C:\pwb\compat\dup.py", line 912, in main bot.run() File "C:\pwb\compat\dup.py", line 751, in run self.run_check() File "C:\pwb\compat\dup.py", line 718, in run_check self.build_table(True) File "C:\pwb\compat\dup.py", line 637, in build_table keys.sort(key=f) File "C:\pwb\compat\dup.py", line 613, in f r = int(table[k][0][2].editTime()) ValueError: invalid literal for int() with base 10: '2013-10-04T15:37:49Z' Release version: 1.0b1 Python: 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)] config-settings: use_api = True use_api_login = True unicode test: ok
Change 88235 had a related patch set uploaded by Mpaa: Bug 55399 Timestamp retrieved by special:export on bulk is no longer yyyymmddhhmmss https://gerrit.wikimedia.org/r/88235
Not sure if this might apply to core as well.
Change 88235 merged by Xqt: Bug 55399 Timestamp retrieved by special:export on bulk is no longer yyyymmddhhmmss https://gerrit.wikimedia.org/r/88235
