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 p-ganssle
Recipients belopolsky, eamanu, lemburg, matrixise, p-ganssle
Date 2019-02-17.18:07:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The attached PR is more or less fully ready, I think the correct answers to 1, 3 and 4 are that we should go with 3 separate arguments and we should not allow either time components or tz components, at least in this version.

In the future, I don't think it will be backwards incompatible to add in these features if they are desired (though I imagine they won't be terribly in demand, and it's pretty easy to work around).

The only real remaining question is number 2. Right now I am allowing keyword arguments, but the only real value I see in doing that is that PEP 570 (positional-only parameters) is not done yet and it's kind of annoying to implement "positional only parameters" in the pure Python version. If anyone feels strongly about this, let me know, otherwise I'll switch the implementation over to positional-only parameters.
Date User Action Args
2019-02-17 18:07:49p-gansslesetrecipients: + p-ganssle, lemburg, belopolsky, matrixise, eamanu
2019-02-17 18:07:49p-gansslesetmessageid: <>
2019-02-17 18:07:49p-gansslelinkissue36004 messages
2019-02-17 18:07:49p-gansslecreate