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 steven.daprano
Recipients haneef95, steven.daprano
Date 2017-10-30.01:54:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509328492.84.0.213398074469.issue31895@psf.upfronthosting.co.za>
In-reply-to
Content
Python 2.7 is in feature freeze, so 3.7 is the absolute earliest this could be introduced. Given how close we are to 3.7 feature freeze, 3.8 is more likely.

I don't think we would have any objections to supporting hijri calendar, in principle, but as a practical matter I expect that none of the core developers are probably qualified to write, review, support and maintain it. (I could be wrong, of course.) And what interface is required?

I'm not convinced that the datetime module is the right place for this. In the long run, we should expect that Python may support multiple calendars: Western, Arabic, Jewish, Asian calendars, and more. I think that would make datetime too big and clunky.

I think the best approach would be to provide a third-party package on PyPI, and once it has proven itself, it could be proposed for the standard library.
History
Date User Action Args
2017-10-30 01:54:52steven.dapranosetrecipients: + steven.daprano, haneef95
2017-10-30 01:54:52steven.dapranosetmessageid: <1509328492.84.0.213398074469.issue31895@psf.upfronthosting.co.za>
2017-10-30 01:54:52steven.dapranolinkissue31895 messages
2017-10-30 01:54:51steven.dapranocreate