Currently, the docs for the Printf standardlib simply mentions it uses "C printf style format specification", but does not specify what that is, nor provides a link to the C printf format.

It would be nice to explain it in the docs.

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

astropy/astropy#9468 highlighted that there are code snippets in docstrings that are not actually picked up during doctesting. I strongly feel that shouldn't be the case, we should skip any such testing in very rare occasions.
I tag this as a coordinates issue, but they may be other sub packages affected by the same problem.

Is your feature request related to a problem? Please describe.
I'm studying geosat flares (link, link) and want to have a better idea of the cone of darkness that is created at a given distance.

Describe the solution you'd like
I want to select an object (satellite, moon, even planet) and see the

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

Should be subtractBarTexture

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