decimal | Arbitrary-precision fixed-point decimal numbers in go | Math library

When making a graph, ggplot2 has a lot of sensible defaults for scales that require extra work when trying to achieve the same result using scales.

An example:

I have an precision issue when dealing with currency input using Decimal type. The issue is with the formatter. This is the minimum reproducible code in playground:

I need to calculate the square root of some numbers, for example √9 = 3 and √2 = 1.4142. How can I do it in Python?

The inputs will probably be all positive integers, and relatively small (say less than a billion), but just in case they're not, is there anything that might break?

Related

• Integer square root in python
  • How to find integer nth roots?
• Is there a short-hand for nth root of x in Python?
• Difference between **(1/2), math.sqrt and cmath.sqrt?
• Why is math.sqrt() incorrect for large numbers?
• Python sqrt limit for very large numbers?
• Which is faster in Python: x**.5 or math.sqrt(x)?
• Why does Python give the "wrong" answer for square root? (specific to Python 2)
• calculating n-th roots using Python 3's decimal module
• How can I take the square root of -1 using python? (focused on NumPy)
• Arbitrary precision of square roots

_{Note: This is an attempt at a canonical question after a discussion on Meta about an existing question with the same title.}

Recently, I was reading about the Ancient Babylonian Civilization that used a number system with base 60 instead of base 10. Even with this number system at base 60, they were still able to approximate the square root of 2 — and that too, thousands of years ago!

I was curious about this, and wanted to see how numbers from our decimal system (base 10) can be converted into the sexagesimal system (base 60). Using the R programming language, I found this link in which an answer is provided on converting numbers from some base to a different base.

However, it seems here that the base can only be between 2 and 36 (I want base 60):

I try to make an ESDT token issuance transaction using the following Python code

I would like to extract the unit of measurement (decimal degrees, metres, feet, etc.) from a spatial object in R. For example, if I have an SF data frame that uses the WGS84 co-ordinate reference system (EPSG:4326), I would like to be able to determine that the co-ordinates are specified in decimal degrees. Similarly, I'd like to be able to determine that UTM co-ordinates (e.g. EPSG:32615) are specified in metres.

I have tried using the st_crs() function from the sf package, which returns the co-ordinate reference system in well-known text format. However, I'm struggling to be certain that a regex that extracts the unit of measurement from that well-known text will operate reliably for a wide range of co-ordinate systems.

Is there an existing function that returns the measurement unit for a spatial object?

For example, the following code produces an SF data frame that uses the WGS84 co-ordinate system:

I have a large piece of text that is missing spaces after some of the periods. However the text also contains decimal numbers.

Here's what I have so far to fix the problem using regex (I'm using python):

re.sub(r"(?!\d\.\d)(?!\. )\.", '. ', my_string)

But the first escape group doesn't seem to work. It still matches periods in decimal numbers.

Here is sample text to make sure any potential solution works:

This is what I've tried at the ghci REPL (stack ghci 8.10.7)