Reference: JuliaLang/julia#38892 (comment)

We accidentally exported HTML and we should warn users to avoid them.

The following behavior was introduced in 1.7.

simplify in some circumstances transforms sign(x) into a Piecewise involving x / Abs(x); somehow this transformed expression can lead to incorrect solutions from solve and solveset.

Consider, e.g., f(x) = x * sign(x), which has a zero at x == 0. After simplifying, even though the Piecewise function explicitly states the case `f

Description

The current docstring in the Spinner class demonstrates using s.next() to update the spinner. But this is a Python 2-ism that no longer exists for iterators in Python 3. Instead the correct documentation would be next(s).

Additionally, I think it's confusing

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

make MicrobeStage QuickSave() not allow quicksaving before stage is loaded and potential autosave is complete

For the long term, we could clean up the code base a bit by internally using pathlib instead of os.path.join(....) and consorts. This is no vital or overly important task but it will help new contributors, to use it in new contributions and not introduce more old-style code, looking at the rest of the code base.

This is a pretty trivial (but longish) task and is a good first issue for new peo

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