Message 335661 - Python tracker

Message335661

Author	p-ganssle
Recipients	belopolsky, eamanu, lemburg, matrixise, p-ganssle
Date	2019-02-16.00:15:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1550276142.97.0.28206630108.issue36004@roundup.psfhosted.org>
In-reply-to

Content
I have a first-pass PR, a few questions to address: 1. Should it take three arguments or a single 3-tuple? (I've gone with 3 arguments) 2. Since all three arguments are required, should we make them positional-only? 3. Should we allow time components in the `datetime` flavor of this? If so, I think we would also want datetime.isocalendar() to return a longer tuple, which would be backwards incompatible. 4. Should we add a `tz` argument in the datetime flavor? I think for questions 3 and 4 the answer is no, modelling after .toordinal/.fromordinal.

Content

I have a first-pass PR, a few questions to address:


1. Should it take three arguments or a single 3-tuple? (I've gone with 3 arguments)
2. Since all three arguments are required, should we make them positional-only?
3. Should we allow time components in the `datetime` flavor of this? If so, I think we would also want datetime.isocalendar() to return a longer tuple, which would be backwards incompatible.
4. Should we add a `tz` argument in the datetime flavor?

I think for questions 3 and 4 the answer is no, modelling after .toordinal/.fromordinal.

History
Date	User	Action	Args
2019-02-16 00:15:43	p-ganssle	set	recipients: + p-ganssle, lemburg, belopolsky, matrixise, eamanu
2019-02-16 00:15:42	p-ganssle	set	messageid: <1550276142.97.0.28206630108.issue36004@roundup.psfhosted.org>
2019-02-16 00:15:42	p-ganssle	link	issue36004 messages
2019-02-16 00:15:42	p-ganssle	create