-
Notifications
You must be signed in to change notification settings - Fork 49
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
modernize pager code #445
Comments
Let me add that I don't think the issue is likely to happen at all in regular deployments... I am testing in barebone docker containers that do not have |
I was just having a discussion with a local user today who said that when they used a function like |
Adding to Doug's notebook example, a CIAO helpdesk user [ref 21322] is running sherpa via spyder and ran into the same problem that |
should we make this a higher priority? |
I am okay with increasing the priority, but I haven't looked at your road map to see how this fits in. Note that there is a chunk of work we could do to make Sherpa work "better" within notebooks (e.g. #345 #347 but I haven't done an exhaustive check to see if there are more), but not for Sherpa 4.11 unless we get external contributors working on it. I don't think it should a big job code-wise, but maybe more work on the policy/API-design side (i.e. what we want to happen and how to control things). |
I've just tried out the |
While testing the 4.10.0 conda binaries I ran into an issue with the utility function that displays information from sherpa in a pager:
sherpa/sherpa/ui/utils.py
Line 98 in 8e96fb6
There is a lot of hard-coded logic that can be replaced with something more robust. I quickly gave a look around and found this:
https://stackoverflow.com/a/37585086
The text was updated successfully, but these errors were encountered: