post for tomorrow gets published today

[markuszoeller]

I write blog posts with pre-defined publishing dates. If this date is tomorrow, the publishing happens today, which is 1 day too early.

steps to reproduce

Create a post with tomorrow's date (example assumes that today is October the 5th):

.. post:: Oct 6, 2017
   :title: this is a title

Build the sources ablog build

expected result

The post is not published

actual result

The post is listed in the recent posts section

Recent posts
============

.. postlist:: 5
   :excerpts:
   :date: %b %d, %Y
   :list-style: circle

root cause

The variable TOMORROW gets created with time, while the post.date is a datetime object without time. Examples:
A print statement after this line https://github.com/abakan/ablog/blob/87933fa874680129986c5fff54518d83c753c07b/ablog/blog.py#L89

print('TOMORROW = %s', TOMORROW)   # added for debug

results in this output:

('TOMORROW = %s', datetime.datetime(2017, 10, 6, 7, 34, 2, 150817))

while the print statement after this comparison at https://github.com/abakan/ablog/blob/87933fa874680129986c5fff54518d83c753c07b/ablog/blog.py#L239

print('post date: %s', post.date)  # added for debug

results in this output:

('post date: %s', datetime.datetime(2017, 10, 6, 0, 0))

In short, the post date of tomorrow will always be older than the TOMORROW variable.

possible fix

This (ugly) diff shows one way to do it:

--- blog.py	2017-10-05 20:19:08.405927051 +0200
+++ blog.py.new	2017-10-05 20:10:42.842425856 +0200
@@ -87,6 +87,7 @@
 
 
 TOMORROW = datetime.today() + dtmod.timedelta(1)
+TOMORROW = TOMORROW.replace(hour=0, minute=0, second=0, microsecond=0)
 FUTURE = datetime(9999, 12, 31)
 
 

When we remove the time information of TOMORROW, the comparison works and a post for tomorrow gets only published tomorrow.

[nabobalis]

A new version of Ablog (v0.9.0) is out at this repo.

We did take your fix!