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.

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

A warning (not explicitly a DeprecationWarning) was added in #2719 for #2528; current usage here.

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

It is almost always considered a bad practice to manually invoke a __magic__ method on a class.

# Bad
my_str = my_object.__str__()
# Good
my_str = str(my_object)

A warning for this type of issue could be nice and instructive for people who are new to Python.

Desired solution

A warning is given when Pylint is run on code that invokes __magic__ methods

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 tests group.
2. The .pre-commit-config.yaml. This file is not able to parse previous one, so dependencies need to

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

Conda environment became sluggish, and it is even causing failures in the Continuus-integration tests : the conda environemnt crashes during build . https://app.travis-ci.com/github/radis/radis/jobs/562227307 (fails #422)

💡 Possible solutions

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