Python 3.10 added suggestions for AttributeError and NameError in the error messages. It seems the suggestions are not stored in the exception object but calculated when Error is displayed. There is a note that that this won't work with IPython but it will be good to see if it's feasible. Opening an issue for discussion.

https://bugs.python.org/issue38530
https://docs.python.org/3/whatsnew/3.

It seems like the recording rule panel doesn't have the necessary styling applied to it in the dark mode:

Is possible know the mathematical definition of this function?
scipy.special.chndtr
scipy.special.chndtrix

Also this functions:
scipy.special.nctdtr
scipy.special.nctdtrit

Now that #3490 has been merged, we should add more prometheus metrics to the notebook server!

Some ideas for metrics to add...

1. Number of kernels running (labeled by type)
2. Number of sessions open (not sure if this is useful?)
3. Number of terminals open
4. Mirror of the activity tracking metrics
5. Kernel start / stop latency metric

Current problem

The SEO for individual message start to take effects :

Result:

But we lack some information to easily navigate. The information I

Feature Request

Is your feature request related to a problem? Please describe.

Whenever I report a bug, I need to confirm what satpy version I am using. This is of course important, but it's also an extra step that could be semi-automated.

Describe the solution you'd like

I would like that debug_on() prints the relevant versions. When we report bugs, we anyway call `debu

Many issues we run into (e.g. freshish ReproNim/containers#62) with git-annex stem from "exotic" filesystems, often used on HPC, and which could be proprietary and cannot be setup within our CI to be tested against. When users report problems, and even share WTF information, it requires inquiring more to discover specific of the filesystem in question and possibly releva

Code Sample, a minimal, complete, and verifiable piece of code

from pyresample.boundary import Boundary
b = Boundary(my_lons, my_lats)
print(b.contour_poly.area())

Problem description

The above code doesn't fail if the provided lons/lats are 2D (not sure on 3D+), but the class and all functions/utilities underneath it assume 1D arrays. The end results are incor

Description of the problem

As in the tutorial description here, we say, "we plan to add some more examples showing usage of pydatastructs on real world data sets such as Stanford Large Network Dataset Collection and Urban Dictionary Wo

🎯 Todo

For the parsers in io.hitran, only groups 1-2 and classes 1, 4-6 are implemented.
Notably, group 6 and class 3 are missing which are needed for linear diatomic molecules.
But this is surprising to me as I never had issues with this... am I missing something?

How they should be parsed can be found in the HITRAN2004 paper:
https://hitran.org/media/refs/HITRAN-2004.pdf
tables 3 & 4

The IS2_DEM_comparison_WIP.ipynb notebook is still in the repo, but is not shown on the docs page because it is too outdated. icepyx now has some of the functionalities (e.g. data read in) that previously relied on other 2019 hackweek libraries, and the DEM used in the comparison cannot be shared publicly (though it is freely available to download). We need to migrate this example to a more easily

Notebook proposal

Title: Reinforcement Learning Model for behavioral data

Why should this notebook be added to pymc-examples?

I wrote this notebook some time ago: https://github.com/ricardoV94/stats/blob/master/modelling/RL_PyMC.ipynb and shared it on the Discourse, where it seems to have been quite popular: https://discourse.pymc.io/t/fitting-a-simple-reinforcement-learning-model-to-be

As our examples grow they becomes a bit harder to navigate. Might be good to think about organizing them better. Maybe a (max 1 layer deep) dir structure, or just more sensible names.

Related, I really like how the Threejs examples can be searched by keyword. Maybe something for our docs? (Technically a separate issue.)