This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients gdr@garethrees.org, haneef95, lemburg, steven.daprano, terry.reedy
Date 2017-11-03.20:51:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509742267.72.0.213398074469.issue31895@psf.upfronthosting.co.za>
In-reply-to
Content
Haneef, thank you for the explanation.  Any such addition would need a PEP.  But I agree with Marc-Andre that supporting the multitude of calendars is out of scope for the stdlib.  So I suspect such a PEP would be rejected, with the suggestion already given here, that this belongs on PyPI.  An existing example is the time module of the astropy module,
http://docs.astropy.org/en/stable/time/index.html .

I could be wrong, but I have a vague impression that expanding calendar support has been requested and rejected before.  We have enough to do properly supporting the existing time, datetime, and calendar modules.
History
Date User Action Args
2017-11-03 20:51:07terry.reedysetrecipients: + terry.reedy, lemburg, steven.daprano, gdr@garethrees.org, haneef95
2017-11-03 20:51:07terry.reedysetmessageid: <1509742267.72.0.213398074469.issue31895@psf.upfronthosting.co.za>
2017-11-03 20:51:07terry.reedylinkissue31895 messages
2017-11-03 20:51:07terry.reedycreate