Hans Moritz Günther
Hans Moritz Günther
Hi, I wonder if we should take #2174. Python 3.13 is going to be released well before Sherpa 4.17 makes it out to most users as part of CIAO 4.17....
I want to push that I we should update (from 4.17.1 to the next number) and merge this as the next PR after the release is cut and we continue...
This would close #555
First thoughts, without the deep dive that will be needed: 1. Since for `sherpa.data.Data`, `eval_model` and `eval_model_to_fit` only differ in the value of `filter` that is passed on, I wonder...
"cost effective" not just as in $, but even more importantly in "developer time" which is far more valuable!
I think this is the right direction to go, though I also agree with the priority:low label.
This has partially been addressed by #2126. Should we close or keep open for the thoughts about squeezing model components into the same `plot` calls?
There are so many open PRs that it's hard to keep track which one is in my court and which one is back on @DougBurke. Here, @DougBurke says ["need to...
This is almost, but not exactly, a dublicate of https://github.com/sherpa/sherpa/issues/1406, in particular see [Kislat et al. (2015)](https://ui.adsabs.harvard.edu/abs/2015APh....68...45K/abstract) eqn 49.
In the even more unlikely event that we're still here when 3.13. is the minimum version we support.... I think this is one of those cases where we might just...