Recent discussions on Discourse suggest that not all users know about apropos (or equivalently, using ?"..." for text search). The startup message currently mentions

Type "?" for help, "]?" for Pkg help.

I suggest that text search is added to this, but I am still looking for a compact way of phrasing it.

Consider the following system and its solution:

from sympy import *
from sympy.abc import j,f

# augmented matrix
a=Matrix([
[1,  1, 1,  1, 1,  1, 1,  1,  1],
[0, -1, 0, -1, 0, -1, 0, -1, -j],
[0,  0, 0,  0, 1,  1, 1,  1,  f]
])

x=Matrix(list(linsolve(a))[0])

# check if x is a solution
a[:,:-1]*x-a[:,-1] # should be all 0 but the second term is 'tau0-tau1'

Do you have an

you are right that we should add [np.full] to the known issues. One similarly cannot do np.zeros, np.ones, and np.empty.

Originally posted by @mhvk in astropy/astropy#10836 (comment)

The list in question: https://docs.astropy.org/en/latest/known_issues.html#quantities-lose-their-units-with-some-operations

Hi. I can imagine calendar options that would allow people to try different types of calendars. For example with lunar calendars like the Chinese, Vietnamese, Hindu, and Thai calendars.
I see this a powerful aid in teaching the importance of calendars and how they can help us relate to cosmic influences.
By the way... stellar work so far!

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

🙋 Feature Request

🔦 Context

What is the feature ?

I'm trying out this library for the first time and I'm seeing several places where some shorthand functions would have been really pleasant:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. My plots are supposed to be white-on-black, which requires a lot of boilerplate on lots o

I'll show a brief program below. The program demonstrates unclear/consistent behavior of the size, width and height arguments when creating a new Rect. Using the argparse module, the user can easily create a rectangle using the size argument. When the program isn't given any argument, the width and height argument of Rect() are used and then the the proper size is used for the rectangle, if the

The auto-evo run start should be delayed until auto save has happened (or if auto-save is not on, until the fade is complete).

I can see there is already a related/similar issue with this [(https://github.com/obspy/obspy/pull/2420 )] but since it has not been finalized I would create a new one.
I am not able to include stationMagnitude to the catalog conversion with my GSE2 format catalog. I thought it was because of my catalog. It might have some formatting problem but I tested it with the example file which was given i

We either do this all ourselves or do some reordering somewhere, I forget. But we should use the LaTeXML option now! brucemiller/LaTeXML#1044