I just noticed the Random stdlib has an UnsafeView type for filling arrays. With the new layout optimizations, this should no longer be necessary. We should try using the normal SubArray type for this. If it's still too slow/complex, then at least the type can be made safe by holding the underlying array directly instead of a Ptr.

PR #11510 introduced some method to fixing the problems that the dsolve faced to solve systems of ODEs. But, it has already been solved by the solvers added in the past few months.

We want to remove the PR but there are some test cases added in the PR that can be used to check the current functionality added. We want test cases added in `te

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.

I am suggesting adding up another feature which will be either a standalone or a part of an advanced search. I suggest adding up a tool which will permit to select a given area. A user can predefine searchable objects by their type (like dwarfs, blue giants and the like) and magnitude (all objects of the apparent/absolute magnitude, for example, 13). When search is done, the search box would list

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

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

I've noticed whilst using the Parser function with .dlseed file type that the error 'First byte of data must be in [0-9<]' occurs when an incorrect directory name is entered. This can make it hard to identify whether your file type is corrupt, or that you've entered a wrong directory name

I'd like to make the developers aware, so they can include an error line that identifies an incorrect direc

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