-
-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
param.Date no longer uses pn.widgets.DatePicker #1271
Comments
It seems
Moreover, there was some discussion over at param on how to organize a parameter that specified a datetime vs a date a little while ago, and I believe they settled with
As far as this goes, it seems that the underlying pn.widgets.DatePicker uses param.Date for the default value and bounds under the hood, which may lead to some not straightforward errors. I think these parameters should be changed to Sorry for the super long response! I've had my fair share of scratching my head with panel/param and Dates. |
Thanks! I think I agree with all of that, i.e. that the real fixes needed are:
We may also want to:
|
It would be great if possible for someone to address various param datetime woes together: https://github.com/holoviz/param/labels/datetimes. Skimming those just now, I also don't see any mention of timezone-aware vs. unaware datetimes, timedeltas, etc etc, which it would be great to consider at the same time (even if just to dismiss). (I suppose panel could also have the extra pain to consider of "browser datetime" vs "python process datetime", in case they are different...but that could just be a friendly note to add to documentation, for people creating applications to think about.) |
My Pain
I'm trying to develop a parameterized class with a
param.Date
parameter. When I show the parameter usingpn.Param
I dont get theDatePicker
just a simple input.See example at https://panel.holoviz.org/user_guide/Param.html
Additional Context
If I try to specify the parameter as
pn.widgets.DatePicker
directly I get aValueError: Expected a date value, got a datetime.datetime
so maybe something has changed with the new DatePicker.The text was updated successfully, but these errors were encountered: