closember

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.

The idea originated from this comment, see for full context thanos-io/thanos#4908 (comment)

Basically, we could improve the user experience by providing more information on how the stores are being queried, beyond providing just min / max time or just showing that the min / max time is not available, which does not in fact tell users if that store will be que

Hi!

This line requires the length of bands to be even:

https://github.com/scipy/scipy/blob/b5d8bab88af61d61de09641243848df63380a67f/scipy/signal/_fir_filter_design.py#L982

But from the docs, and the example that uses a flattened sequence as bands (see below), it's not that obvious that firls requires an even number of edges. Could this be improved/clarified in the docs? Thank you!

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

A longstanding issue of pylint has been that there is little documentation about some of the messages and why they are emitted. For some messages the short message that is displayed is not enough to make explicit what needs to be changed or what is considered wrong.
With the closure of #5527 and the merge of #5934 we have now set up a system that allows us to do so!
We have also received the o

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

💡 Feature request

At the moment, there are three separate files holding coding style requirements:

1. The pyproject.toml. In this file, it is possible to find the style requirements in the dev group.
2. The .pre-commit-config.yaml. This file is not able to parse previous one, so dependencies need to b

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

🐛 Describe the bug

Adding the link to Radis-Lab issues & features. Good first issues for those who are familiar with Python and Jupyter Notebook.

A specific good first issue for those who are familiar or want to learn docker: https://github.com/radis/radis-lab/issu

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

It should be the same as pymc-devs/pymc#5486 but here in pymc-examples.

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.)

#94 introduce the <module_name>.expected_errors, which has a mapping of error names to which object fail with those.

In particular this will allow us to track when some errors get fixed (in papyri or upstream).

Other files, use the exclude = [list of str] option, which is impractical as it does not tell us whether the failure are still happening or not.

For all files that have a lo