Hi all! If you wonder about the lack of progress reports on pep-431, this is because of a lack of progress. I simply haven't had any time to work on this. I considered make a kickstarter so I could take time off from working, but to be honest, even with that, I still have no time to realistically get this in before beta 1. Sorry about that! //Lennart
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro <regebro@gmail.com> wrote:
If you wonder about the lack of progress reports on pep-431, this is because of a lack of progress. I simply haven't had any time to work on this. I considered make a kickstarter so I could take time off from working, but to be honest, even with that, I still have no time to realistically get this in before beta 1.
Is there a list of stuff that needs to be done? I might be able to help out. Cheers, Dirkjan
On Wed, Oct 2, 2013 at 3:05 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro <regebro@gmail.com> wrote:
If you wonder about the lack of progress reports on pep-431, this is because of a lack of progress. I simply haven't had any time to work on this. I considered make a kickstarter so I could take time off from working, but to be honest, even with that, I still have no time to realistically get this in before beta 1.
Is there a list of stuff that needs to be done? I might be able to help out.
Yes. 1. Implement the PEP. :-) I looked at it during the PyCon sprint, and I had hoped to be able to mostly move pytz into datetime, but unfortunately it wasn't that easy, because of the way datetime normalization works. The pytz normalization calls methods that would need to call the normalization... :-) //Lennart
On Wed, Oct 2, 2013 at 9:42 PM, Lennart Regebro <regebro@gmail.com> wrote:
On Wed, Oct 2, 2013 at 3:05 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro <regebro@gmail.com> wrote:
If you wonder about the lack of progress reports on pep-431, this is because of a lack of progress. I simply haven't had any time to work on this. I considered make a kickstarter so I could take time off from working, but to be honest, even with that, I still have no time to realistically get this in before beta 1.
Is there a list of stuff that needs to be done? I might be able to help out.
Yes.
1. Implement the PEP.
:-)
I looked at it during the PyCon sprint, and I had hoped to be able to mostly move pytz into datetime, but unfortunately it wasn't that easy, because of the way datetime normalization works. The pytz normalization calls methods that would need to call the normalization... :-)
I think the first thing that needs to happen is get the is_dst flag in. Then we can turn pytz into a new, sane API without all that awful normalization stuff :) It doesn't all have to land in the same release.
That could be a possibility as well. On Wed, Oct 2, 2013 at 6:14 PM, Stuart Bishop <stuart@stuartbishop.net> wrote:
On Wed, Oct 2, 2013 at 9:42 PM, Lennart Regebro <regebro@gmail.com> wrote:
On Wed, Oct 2, 2013 at 3:05 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
On Wed, Oct 2, 2013 at 2:17 PM, Lennart Regebro <regebro@gmail.com> wrote:
If you wonder about the lack of progress reports on pep-431, this is because of a lack of progress. I simply haven't had any time to work on this. I considered make a kickstarter so I could take time off from working, but to be honest, even with that, I still have no time to realistically get this in before beta 1.
Is there a list of stuff that needs to be done? I might be able to help out.
Yes.
1. Implement the PEP.
:-)
I looked at it during the PyCon sprint, and I had hoped to be able to mostly move pytz into datetime, but unfortunately it wasn't that easy, because of the way datetime normalization works. The pytz normalization calls methods that would need to call the normalization... :-)
I think the first thing that needs to happen is get the is_dst flag in. Then we can turn pytz into a new, sane API without all that awful normalization stuff :) It doesn't all have to land in the same release.
That's a shame, but there's always 3.5 and we'll hopefully have an easier path to "pip install pytz" in 3.4 (once I get PEP 453 revised appropriately). Cheers, Nick. On 2 October 2013 22:17, Lennart Regebro <regebro@gmail.com> wrote:
Hi all!
If you wonder about the lack of progress reports on pep-431, this is because of a lack of progress. I simply haven't had any time to work on this. I considered make a kickstarter so I could take time off from working, but to be honest, even with that, I still have no time to realistically get this in before beta 1.
Sorry about that!
//Lennart _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (4)
-
Dirkjan Ochtman -
Lennart Regebro -
Nick Coghlan -
Stuart Bishop