summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/release/upcoming_changes/19805.new_feature.rst5
-rw-r--r--numpy/f2py/tests/test_crackfortran.py4
2 files changed, 7 insertions, 2 deletions
diff --git a/doc/release/upcoming_changes/19805.new_feature.rst b/doc/release/upcoming_changes/19805.new_feature.rst
new file mode 100644
index 000000000..f59409254
--- /dev/null
+++ b/doc/release/upcoming_changes/19805.new_feature.rst
@@ -0,0 +1,5 @@
+Symbolic parser for Fortran dimension specifications
+----------------------------------------------------
+A new symbolic parser has been added to f2py in order to correctly parse
+dimension specifications. The parser is the basis for future improvements
+and provides compatibility with Draft Fortran 202x.
diff --git a/numpy/f2py/tests/test_crackfortran.py b/numpy/f2py/tests/test_crackfortran.py
index da7974d1a..b1503c1e0 100644
--- a/numpy/f2py/tests/test_crackfortran.py
+++ b/numpy/f2py/tests/test_crackfortran.py
@@ -170,7 +170,7 @@ class TestMarkinnerspaces():
class TestDimSpec(util.F2PyTest):
- """This test site tests various expressions that are used as dimension
+ """This test suite tests various expressions that are used as dimension
specifications.
There exists two usage cases where analyzing dimensions
@@ -183,7 +183,7 @@ class TestDimSpec(util.F2PyTest):
`lower` and `upper` are arbitrary expressions of input parameters.
The evaluation is performed in C, so f2py has to translate Fortran
expressions to valid C expressions (an alternative approach is
- that a developer specifies the corresponing C expressions in a
+ that a developer specifies the corresponding C expressions in a
.pyf file).
In the second case, when user provides an input array with a given