Modify rule S6331: Add Python as covered language (#798)

rules/S6331/description.adoc

@@ -1,6 +1,6 @@
 There are several reasons to use a group in a regular expression:
 
-* to change the precedence (e.g. ``++/do(g|or)/++`` will match 'dog' and 'door')
+* to change the precedence (e.g. `do(g|or)` will match 'dog' and 'door')
 * to remember parenthesised part of the match in the case of capturing group
 * to improve readability
 

rules/S6331/implementation.adoc

@@ -0,0 +1,17 @@
+ifdef::env-github,rspecator-view[]
+
+'''
+== Implementation Specification
+(visible only on this page)
+
+== Message
+
+Remove this empty group.
+
+== Highlighting
+
+The empty group should be highlighted.
+
+'''
+
+endif::env-github,rspecator-view[]

rules/S6331/php/rule.adoc

@@ -14,20 +14,4 @@ include::../description.adoc[]
 "/foo\(\)/"  // Matches 'foo()'
 ----
 
-ifdef::env-github,rspecator-view[]
+include::../implementation.adoc[]
-
-'''
-== Implementation Specification
-(visible only on this page)
-
-== Message
-
-Remove this empty group.
-
-== Highlighting
-
-The empty group should be highlighted.
-
-'''
-
-endif::env-github,rspecator-view[]

rules/S6331/python/metadata.json

@@ -0,0 +1,2 @@
+{
+}

rules/S6331/python/rule.adoc

@@ -0,0 +1,17 @@
+include::../description.adoc[]
+
+== Noncompliant Code Example
+
+[source,python]
+----
+r"foo()" # Noncompliant, will match only 'foo'
+----
+
+== Compliant Solution
+
+[source,python]
+----
+r"foo\(\)" # Matches 'foo()'
+----
+
+include::../implementation.adoc[]