WIP: bpo-1100942: Add datetime.time.strptime and datetime.date.strptime#5578
WIP: bpo-1100942: Add datetime.time.strptime and datetime.date.strptime#5578matrixise wants to merge 16 commits into
Conversation
|
This PR is for a very long issue, since 2005. We have a PR in 2018 👍 |
Sorry, something went wrong.
|
I restarted the travis job. It still did not do the full CPython test suite. So please rebase :) |
Sorry, something went wrong.
|
Thanks, I didn't see your message, works on this issue today. |
Sorry, something went wrong.
ad32c42 to
a7b624a
Compare
February 15, 2018 08:23
|
Hi @pganssle thank you for your review, I am going to fix it asap but I am not the author of the code, just the author of the PR. so, maybe I would need your help. Thanks |
Sorry, something went wrong.
|
@pganssle I just rebased my branch with master. I am going to work on this PR. Do you want to help me because you are mister dateutil ;-) |
Sorry, something went wrong.
|
@matrixise Sorry this is on my list but probably can't get to it until the end of the month. 😟 |
Sorry, something went wrong.
|
@pganssle ok, in this case, I will try to fix all the issues alone ;-) but I am not worried ;-) |
Sorry, something went wrong.
1d7a5b0 to
c286708
Compare
October 17, 2018 19:56
|
Hi, I just updated this PR with master. |
Sorry, something went wrong.
a6722e7 to
7526de9
Compare
October 25, 2018 14:02
|
@pganssle when you have time, could you review this PR, we started together, just comment when you find a mistake, thanks |
Sorry, something went wrong.
pganssle
left a comment
There was a problem hiding this comment.
I haven't had a chance to look at the PR thoroughly, but I have a first-pass review of things that should be changed.
I also haven't checked exactly how you are doing it, but I believe we may want to / be able to refactor the tests a bit to take advantage of the existing test suite for datetime.strptime by separating out the date-only and time-only formats and reusing the tests with date, time and datetime.
Additionally, I should note that it's unfortunate that if this is merged, we'll have time.strptime and datetime.time.strptime, the first of which returns a timetuple (which is actually more like a datetime), and the second returning a datetime.time object. I don't see any way around this, but it will add confusion. :(
Sorry, something went wrong.
|
@pganssle thanks for your review, I am going to update this PR asap. |
Sorry, something went wrong.
1ca284e to
43a77af
Compare
November 11, 2018 14:15
|
ok, rebased with the last master. |
Sorry, something went wrong.
|
ok, I will check and try to fix that, but because I don't know this part
and the main patch was not mine, that will be difficult.
but okay for the fix. thanks for the review.
|
Sorry, something went wrong.
|
@pganssle Are you ready for a new review of this PR? I will continue my PR ;-) |
Sorry, something went wrong.
vadmium
left a comment
There was a problem hiding this comment.
I suggest you check the discussion about the previous patches. I noticed I repeated some old comments and ideas.
Sorry, something went wrong.
|
@matrixise, @pganssle There's been a lot of work done on this one. Is it something we should try to move forward on? Thanks! |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
@matrixise, @pganssle, @csabella while there has been lots of work for this where are we at on this? Its around a bit over two years old for the PR but, these new features would be great! |
Sorry, something went wrong.
No activity since 2019. Someone has to step in and restart the work (ex: create a new PR and update the PR). |
Sorry, something went wrong.
|
I'm going to try to resolve the merge conflicts and make the requested changes. |
Sorry, something went wrong.
|
Looks like I'll have to start over. |
Sorry, something went wrong.
|
I close the inactive PR. |
Sorry, something went wrong.
Add datetime.date.strptime and datetime.time.strptime.
Fix the documentation of _strptime._strptime, the documentation was
wrong, return a 3-tuple and not a 2-tuple
Co-authored-by: Alexander Belopolsky alexander.belopolsky@gmail.com
Co-authored-by: Amaury Forgeot d'Arc amauryfa@gmail.com
Co-authored-by: Berker Peksag berker.peksag@gmail.com
Co-authored-by: Josh-sf josh-sf@users.sourceforge.net
Co-authored-by: Juarez Bochi jbochi@gmail.com
Co-authored-by: Maciej Szulik soltysh@gmail.com
Co-authored-by: Stéphane Wirtel stephane@wirtel.be
Co-authored-by: Matheus Vieira Portela matheus.v.portela@gmail.com
https://bugs.python.org/issue1100942