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.

On https://thanos.io/tip/thanos/changelog.md/ -> Table of Contents

This link v0.25.2 - 2022.03.24 should actually go towards https://thanos.io/tip/thanos/changelog.md/#v0252httpsgithubcomthanos-iothanostreerelease-025---20220324

Perhaps this page / table of contents could be easier/nicer as well - For example that the table of contents

Describe your issue.

Currently, applying the ** operator to a sparse array implements the numpy.linalg.matrix_power function. This is not compatible with the np.array implementation of **, which does element-wise power. This should be fixed as part of the migration from sparse "matrices" to sparse "arrays". Additionally, the matrix_power function should then also be included in the

Problem

At the moment the help plugin is all contained in a single plugin:

Bug description

Two issues with bad-string-format-type:

1. Just like bad-format-character the bad-string-format-type message is currently only raised for old-style string formatting.
2. If only a single value needs to be formatted, the check does not work if the value to format is passed in as a variable. Using variables in tuples however is fine.

Given a file a.py:

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

Turning an insightful comment from @AllanHOlesenBW into a Todo/Request.

in short: I think it would be beneficial if the default wunit and Iunit in a spectrum would correspond to each other so a new user can jump directly to work with the units he is given.

Context :

My main expectation is that the unit describing the wavenum/wavelength/frequency corresponds to the dSom

Currently we track (and visualize) GitHub clones and PyPI downloads here. It would be great to add conda-forge data to this. Steps required (draft list):

• build Python script to access/download and visualize data
• determine the best way to do above (likely via this anaconda package data library)
• create a GitHub action t

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

List list a number of edge cases in upstream libraries,
it would be great is upstream would accept to fix them.

They are usually handled by sphinx but add complexity to papyri.

Numpy:

Links that use `<...>` syntax with no text. I think they can be replaced by just `...`

$ rg '[^`]`<.+>`'
doc/RELEASE_WALKTHROUGH.rst.txt
158:provided at `<https://github.com/Mac