You are tagging onto a three year-old issue by someone else and providing less information than was originally provided by the original person posting.
I assume you are using MyBinder? What are you using as a configuration file? Since things that run at MyBinder have to be public it is usually best when posting an issue to include the link to the associated repository. Usually looking at what that gives provides more information than having to post it all here.
My guess without looking though is you are using Python 3.7, and so it won’t work because it sys on the left side of the Python Package Index entry for version 1.4.4 of Pandas, " Requires: Python >=3.8". (Launches from the conda example and with a typical requirements.txt [e.g., here] only give 3.7 at present.) If you had said what sort of configuration file you are using, I could guide you in how to specify the version of Python along with your specified version of Pandas.
Update:
Noting that this was cross-posted here and I tried to further advise there as what was posted there reflected a poor understanding and was short-sighted as it will lead to problems when the default version of Python changes yet again at a future date. If the OP didn’t care about the version of Pandas, which seemed the be the case given the OP’s proposed work-around, then not pinning the version at all is advisable as the current most recent version of Pandas compatible with the current default version of Python will get used. So even as the default version of Python evolves with time, the images backing the sessions should still build without error and launch.