mirror of
https://github.com/JimmXinu/FanFicFare.git
synced 2025-12-22 00:33:59 +01:00
d226f4791f
The correct function since 2003 has been .warning(), and .warn() is a compat wrapper over it. It wasn't documented until https://bugs.python.org/issue13235 added documentation stating it exists but is obsolete. Nevertheless, the whole world is full of code that mysteriously uses it anyway. Let's at least remove it here, though.
85 lines
2.9 KiB
Python
85 lines
2.9 KiB
Python
# -*- coding: utf-8 -*-
|
|
|
|
# Copyright 2018 FanFicFare team
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
#
|
|
|
|
from __future__ import absolute_import
|
|
|
|
from datetime import datetime, timedelta
|
|
|
|
# py2 vs py3 transition
|
|
from .six import text_type as unicode
|
|
|
|
import logging
|
|
logger = logging.getLogger(__name__)
|
|
|
|
## There's a windows / py3 bug that prevents using 0.
|
|
## So Jan 2, 1970 instead.
|
|
UNIX_EPOCHE = datetime.fromtimestamp(86400)
|
|
|
|
## Currently used by adapter_webnovelcom & adapter_wwwnovelallcom
|
|
|
|
def parse_relative_date_string(string_):
|
|
# Keep this explicit instead of replacing parentheses in case we
|
|
# discover a format that is not so easily translated as a
|
|
# keyword-argument to timedelta. In practice I have only observed
|
|
# hours, weeks and days
|
|
unit_to_keyword = {
|
|
'second(s)': 'seconds',
|
|
'minute(s)': 'minutes',
|
|
'hour(s)': 'hours',
|
|
'day(s)': 'days',
|
|
'week(s)': 'weeks',
|
|
'seconds': 'seconds',
|
|
'minutes': 'minutes',
|
|
'hours': 'hours',
|
|
'days': 'days',
|
|
'weeks': 'weeks',
|
|
'second': 'seconds',
|
|
'minute': 'minutes',
|
|
'hour': 'hours',
|
|
'day': 'days',
|
|
'week': 'weeks',
|
|
}
|
|
|
|
# discards trailing ' ago' if present
|
|
value, unit_string = string_.split()[:2]
|
|
unit = unit_to_keyword.get(unit_string)
|
|
if not unit:
|
|
## I'm not going to worry very much about accuracy for a site
|
|
## that considers '2 years ago' and acceptable time stamp.
|
|
if "year" in unit_string:
|
|
value = unicode(int(value)*365)
|
|
unit = 'days'
|
|
elif "month" in unit_string:
|
|
value = unicode(int(value)*31)
|
|
unit = 'days'
|
|
else:
|
|
# This is "just as wrong" as always returning the currentq
|
|
# date, but prevents unneeded updates each time
|
|
logger.warning('Failed to parse relative date string: %r, falling back to unix epoche', string_)
|
|
return UNIX_EPOCHE
|
|
|
|
kwargs = {unit: int(value)}
|
|
|
|
# "naive" dates without hours and seconds are created in
|
|
# writers.base_writer.writeStory(), so we don't have to strip
|
|
# hours and minutes from the base date. Using datetime objects
|
|
# would result in a slightly different time (since we calculate
|
|
# the last updated date based on the current time) during each
|
|
# update, since the seconds and hours change.
|
|
today = datetime.utcnow()
|
|
time_ago = timedelta(**kwargs)
|
|
return today - time_ago
|