Enable ruff RUF001 rule

Author: MaximSmolskiy

fuzzy_logic/fuzzy_operations.py

@@ -150,7 +150,7 @@ def union(self, other) -> FuzzySet:
         FuzzySet(name='a ∪ b', left_boundary=0.1, peak=0.6, right_boundary=0.35)
         """
         return FuzzySet(
-            f"{self.name} ∪ {other.name}",
+            f"{self.name} U {other.name}",
             min(self.left_boundary, other.left_boundary),
             max(self.right_boundary, other.right_boundary),
             (self.peak + other.peak) / 2,

physics/basic_orbital_capture.py

@@ -4,14 +4,14 @@
 
 """
 These two functions will return the radii of impact for a target object
-of mass M and radius R as well as it's effective cross sectional area σ(sigma).
-That is to say any projectile with velocity v passing within σ, will impact the
+of mass M and radius R as well as it's effective cross sectional area sigma.
+That is to say any projectile with velocity v passing within sigma, will impact the
 target object with mass M. The derivation of which is given at the bottom
 of this file.
 
 The derivation shows that a projectile does not need to aim directly at the target
 body in order to hit it, as  R_capture>R_target. Astronomers refer to the effective
-cross section for capture as σ=π*R_capture**2.
+cross section for capture as sigma=π*R_capture**2.
 
 This algorithm does not account for an N-body problem.
 

physics/malus_law.py

@@ -31,7 +31,7 @@
 Real polarizers are also not perfect blockers of the polarization orthogonal to
 their polarization axis; the ratio of the transmission of the unwanted component
 to the wanted component is called the extinction ratio, and varies from around
-1:500 for Polaroid to about 1:106 for Glan–Taylor prism polarizers.
+1:500 for Polaroid to about 1:106 for Glan-Taylor prism polarizers.
 
 Reference : "https://en.wikipedia.org/wiki/Polarizer#Malus's_law_and_other_properties"
 """

pyproject.toml

@@ -10,7 +10,6 @@ lint.ignore = [    # `ruff rule S101` for a description of that rule
   "PLW2901",  # PLW2901: Redefined loop variable -- FIX ME
   "PT011",    # `pytest.raises(Exception)` is too broad, set the `match` parameter or use a more specific exception
   "PT018",    # Assertion should be broken down into multiple parts
-  "RUF001",   # String contains ambiguous {}. Did you mean {}?
   "RUF002",   # Docstring contains ambiguous {}. Did you mean {}?
   "RUF003",   # Comment contains ambiguous {}. Did you mean {}?
   "S101",     # Use of `assert` detected -- DO NOT FIX