The warnings at

https://ipython.readthedocs.io/en/stable/config/extensions/autoreload.html

do not mention the issues with reloading modules with enums:

• Enum and Flag are compared by identity (is, even if == is used (similarly to None))
• reloading a module, or importing the same module by a different name, creates new enums (look the same, but are not the same)

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.

I have enclosed a minimum reproducible example with data and I am trying to use two methods in the scipy optimize package - https://docs.scipy.org/doc/scipy/reference/optimize.html

One is minimize_scalar and the other is Brent's method. But both the outputs have large differences. Can anybody explain why ?

Also I get a runtime error while running Brent-

test.p

Problem

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

Bug description

A little background. The str justify methods (rjust(), ljust(), center()) take SupportsIndex types for width rather than just straight integers, allowing you to use custom types like so.

>>> class Foo:
...     def __index__(self):
...         return 10
... 
>>> 'abcd'.rjust(Foo())
'      abcd'

If you subclass str and re-implement thes

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

During local tests got following test failure

======================================================================
ERROR: datalad.downloaders.tests.test_s3.test_restricted_bucket_on_NDA('s3://NDAR_Central_4/submission_23075/README', 'error', 'BIDS')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.9/url

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 what you'd like

The possibility to plot any variable (radiance, absorbance...) on a double x-axis plot would be really convenient!

💡 Possible implementations

In spectrum.plot the argument wunit could be used.
For exam

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