Patch: xmlrpclib client ignores datetime tzinfo when creating iso8601 dates

Open
#46,875 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reviewing xmlrpclib.py and the linked xmlrpclib-timezone.patch for the ISO 8601 date construction path. Confirm how datetime tzinfo is currently handled, then verify that XML-RPC dates created from timezone-aware datetimes preserve that timezone information.

Written by the indexing model from the issue text.

Description

stdlib topic-XML type-bug
BPO 2623
Files
  • xmlrpclib-timezone.patch: Patch for xmlrpclib.py, adds iso8601 with timezone info
    		•

    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 2008-04-12.06:11:48.707>
labels = ['expert-XML', 'type-bug']
title = 'Patch: xmlrpclib client ignores datetime tzinfo when creating iso8601 dates'
updated_at = <Date 2013-03-20.20:56:25.330>
user = 'https://bugs.python.org/lclark'

    bugs.python.org fields:

    activity = <Date 2013-03-20.20:56:25.330>
actor = 'Thomas Fenzl'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['XML']
creation = <Date 2008-04-12.06:11:48.707>
creator = 'lclark'
dependencies = []
files = ['10016']
hgrepos = []
issue_num = 2623
keywords = ['patch']
message_count = 4.0
messages = ['65394', '65688', '65697', '184795']
nosy_count = 3.0
nosy_names = ['schmir', 'lclark', 'Thomas Fenzl']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2623'
versions = ['Python 2.7', 'Python 3.2']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    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.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.