如何实现正确计算年月日时分秒的算法及修复闰年与日期进位问题

Alright, let's break this down into two key parts: fixing the datetime calculation bugs causing incorrect outputs, and building a solid input wizard with proper error handling. I’ve tackled similar datetime edge cases before, so here’s how to get this right:

Your script likely has gaps in leap year logic, month-day mapping, or cascading carryover handling. Let’s address each issue with tested code:

1.1 Correct Leap Year Check #

Most bugs start here—many implementations skip the century year rule (years divisible by 100 need to also be divisible by 400 to be leap years). Here’s the foolproof check:

def is_leap_year(year):
    if year % 4 != 0:
        return False
    elif year % 100 != 0:
        return True
    else:
        return year % 400 == 0

This correctly flags 2000 as a leap year and 1900 as non-leap, which is crucial for February’s day count.

1.2 Get Valid Days per Month #

Tie the leap year check to February’s day count, and map standard days for other months:

def get_days_in_month(year, month):
    # Index 0 unused to align with 1-12 month numbers
    standard_days = [0, 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31]
    if month == 2 and is_leap_year(year):
        return 29
    return standard_days[month]

1.3 Handle Cascading Datetime Carryover #

This is where your script probably failed to roll over days/months/years correctly. Let’s build a function that adds minutes (easily adaptable for hours/seconds) with full carryover:

def add_minutes(datetime_tuple, minutes_to_add):
    year, month, day, hour, minute, second = datetime_tuple
    
    # Handle minute carryover to hours
    total_minutes = minute + minutes_to_add
    extra_hours = total_minutes // 60
    new_minute = total_minutes % 60
    
    # Handle hour carryover to days
    total_hours = hour + extra_hours
    extra_days = total_hours // 24
    new_hour = total_hours % 24
    
    # Handle day carryover to months/years
    new_day = day + extra_days
    while True:
        days_in_current_month = get_days_in_month(year, month)
        if new_day <= days_in_current_month:
            break
        # Roll over to next month
        new_day -= days_in_current_month
        month += 1
        if month > 12:
            # Roll over to next year
            month = 1
            year += 1
    
    return (year, month, new_day, new_hour, new_minute, second)

Test Your Critical Example #

If you pass (2001, 12, 31, 23, 59, 0) and add 1 minute, this returns (2002, 1, 1, 0, 0, 0)—exactly the expected result.

Users will input messy data, so your wizard needs robust validation and clear feedback. Here’s how to handle it:

2.1 Non-Negotiable Input Validation Rules #

Add checks for every field before running calculations:

• Year: Must be a positive integer (restrict to a reasonable range like 1900–2100 if needed; reject strings/negative values).
• Month: Must be an integer between 1–12 (reject 0, 13, or non-numeric inputs).
• Day: Must be an integer between 1 and the valid days for that month/year (e.g., reject Feb 29 in non-leap years).
• Time: Hours 0–23, minutes/seconds 0–59 (no negative values or out-of-range numbers).

2.2 User-Friendly Error Feedback #

• Real-time validation: As users type, show inline errors (e.g., "Month must be between 1–12" if they enter 13).
• Specific messages: Instead of "Invalid date", say "2023 is not a leap year—February only has 28 days".
• Format guidance: Use separate input fields for year/month/day/hour/minute/second (instead of a single free-text box) to reduce formatting errors.

2.3 Edge Case Handling #

Don’t forget these tricky scenarios:

• Empty inputs: Disable the "Calculate" button until all fields are filled, with a prompt like "Please complete all fields".
• Negative time increments: If your wizard allows subtracting time, build a mirror function for carryover in reverse (e.g., 2020-01-01 00:00:00 minus 1 minute becomes 2019-12-31 23:59:00).
• Extreme dates: Ensure your algorithm handles years like 9999 (the leap year check works for any positive integer, so no extra code needed).

内容的提问来源于stack exchange，提问作者Alexandru Lapusneanu