python / python/cpython

email.utils.parsedate_to_datetime() should return None when date cannot be parsed

Open
#74,866 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 stdlib topic-email type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 30681
Nosy @warsaw, @ncoghlan, @bitdancer, @ambv, @serhiy-storchaka, @sim0nx, @timb07, @miss-islington
PRs
  • python/cpython#2229
  • python/cpython#2254
  • python/cpython#10783
  • python/cpython#22090
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = None
    created_at = <Date 2017-06-15.23:12:43.396>
    labels = ['type-bug', 'expert-email', '3.10']
    title = 'email.utils.parsedate_to_datetime() should return None when date cannot be parsed'
    updated_at = <Date 2020-10-27.07:37:48.458>
    user = 'https://github.com/timb07'
    

    bugs.python.org fields:

    activity = <Date 2020-10-27.07:37:48.458>
    actor = 'serhiy.storchaka'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['email']
    creation = <Date 2017-06-15.23:12:43.396>
    creator = 'timb07'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 30681
    keywords = ['patch']
    message_count = 18.0
    messages = ['296137', '296141', '296153', '296154', '296215', '296226', '296231', '296235', '296361', '301618', '330628', '330648', '376384', '379381', '379412', '379464', '379706', '379742']
    nosy_count = 8.0
    nosy_names = ['barry', 'ncoghlan', 'r.david.murray', 'lukasz.langa', 'serhiy.storchaka', 'sim0n', 'timb07', 'miss-islington']
    pr_nums = ['2229', '2254', '10783', '22090']
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue30681'
    versions = ['Python 3.10']
    

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    Research direction

    Start at the email.utils.parsedate_to_datetime() entry point and inspect how unparseable dates are handled. The change is done when an invalid date returns None as requested; note that the issue records several existing pull requests and a fixed resolution.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    python
    Domain
    backend
    Issue type
    Bug
    Difficulty
    3/5
    Estimated time
    1-2 days
    Activity status
    Stale
    Clarity
    Clearly specified
    Newbie friendliness
    15/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.