[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Change by Senthil Kumaran : -- versions: +Python 3.10 -Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Mark Lawrence added the comment: I like the wording in the patch as it's clearer than the original and so think it should be applied. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8822

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Jakob Malm jakob.m...@gmail.com added the comment: Patch without reflow attached. This is my first patch to CPython. I considered submitting the patch without reflowing the paragraph, to make the changes clearer, but I thought that that would mean more work for the committer, if the patch

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Alexander Belopolsky alexander.belopol...@gmail.com added the comment: -There are two kinds of date and time objects: naive and aware. This +Date and time objects are either naive or aware. This Shouldn't we say datetime and time instead of date and time? There is no tzinfo attribute in date

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Jakob Malm jakob.m...@gmail.com added the comment: Shouldn't we say datetime and time instead of date and time? There is no tzinfo attribute in date objects. Perhaps like this? :class:`datetime` and :class:`time` objects are... -- ___ Python

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

anatoly techtonik techto...@gmail.com added the comment: On Thu, Sep 15, 2011 at 10:42 PM, Alexander Belopolsky rep...@bugs.python.org wrote: Shouldn't we say datetime and time instead of date and time? There is no tzinfo attribute in date objects. Does that mean that if aware `datetime` is

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Alexander Belopolsky alexander.belopol...@gmail.com added the comment: On Thu, Sep 15, 2011 at 4:17 PM, anatoly techtonik rep...@bugs.python.org wrote: .. Does that mean that if aware `datetime` is converted to `date` and then back, the tzinfo information is lost and object implicitly becomes

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Jakob Malm jakob.m...@gmail.com added the comment: I agree with Alexander -- I think the current documentation is sufficient to describe 'naive' and 'aware' date and time objects. The sentence There are two kinds of date and time objects: “naive” and “aware”. is perhaps a bit unfortunate,

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Jakob Malm jakob.m...@gmail.com added the comment: I created a patch with the revised wording. -- keywords: +patch Added file: http://bugs.python.org/file23135/datetime_doc.patch ___ Python tracker rep...@bugs.python.org

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Alexander Belopolsky alexander.belopol...@gmail.com added the comment: On Mon, Sep 12, 2011 at 4:30 PM, Jakob Malm rep...@bugs.python.org wrote: .. I created a patch with the revised wording. Your patch seems to reflow the entire paragraph which makes it hard to review and if applied will

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

anatoly techtonik techto...@gmail.com added the comment: The point was: 1. Create an anchor to definition of naive object 2. Create an anchor to definition of aware object 3. Make definitions stand out from the inline text 4. Create cross-references for naive and aware keywords in text that lead

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Alexander Belopolsky alexander.belopol...@gmail.com added the comment: On Mon, Sep 12, 2011 at 4:36 PM, anatoly techtonik rep...@bugs.python.org wrote: .. 5. Mention the fact: By default all objects are naive, by definition, because they don't have any TZ information, and there are no

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +belopolsky stage: - needs patch versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8822

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

Alexander Belopolsky belopol...@users.sourceforge.net added the comment: 'naive' and 'aware' are key datetime types - they need a proper definition and anchor for crossrefences. The definition is given in the introductory section: There are two kinds of date and time objects: “naive” and

[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced

New submission from anatoly techtonik techto...@gmail.com: 'naive' and 'aware' are key datetime types - they need a proper definition and anchor for crossrefences. If you take a look at http://docs.python.org/library/datetime.html - the definition of distinction between them is too vague and