You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is DatePicker problem or Django's/Python's caching, but when one day passes in real date, DatePicker still uses the same dates as were compiled for the first time. Any clues what could be wrong?
The text was updated successfully, but these errors were encountered:
Hi, I don't know if you still need this, but I've faced a similar thing in the past. The issue is that your piece of code is probably executed when the server starts and doing so it fixes the result of timezone.now(). To solve the problem you need to provide the result in a lazy way. You can use lazy wrapper from django.utils.functional and instead of using timezone.now(), you use lazy(timezone.now, timezone.datetime)().
I need to enable only few dates in calendar and I initiate a form like this:
Not sure if this is DatePicker problem or Django's/Python's caching, but when one day passes in real date, DatePicker still uses the same dates as were compiled for the first time. Any clues what could be wrong?
The text was updated successfully, but these errors were encountered: