In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.

E

Setup

Seen with latest code from git while preparing the 1.73 release on Linux, but applies to all platforms.

Expected behaviour

$ python run_tests.py test_PDB_StructureAlignment.py
Python version: 2.7.15 | packaged by conda-forge | (default, Jul 27 2018, 10:26:36) 
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)]
Operating system: posix linux2
test_PDB_StructureAlignment ... ok

Hi,

Thank you for the great tool. I think this is not a bug.

Recently I upgraded some packages and found my results were different from the previous runs. I figured out that it is caused by different versions of pynndescent (0.4.7 vs 0.5.1), which is recommended to use in UMAP. So I think pynndescent should be included in the output of sc.logging.print_header().

Versions

<d