Fix caching problem / remove ref to defaultOctave

music21/_version.py

@@ -47,7 +47,7 @@
 '''
 from __future__ import annotations
 
-__version__ = '11.0.0b11'
+__version__ = '11.0.0b12'
 
 def get_version_tuple(vv):
     v = vv.split('.')

music21/base.py

@@ -26,7 +26,7 @@
 <class 'music21.base.Music21Object'>
 
 >>> music21.VERSION_STR
-'11.0.0b11'
+'11.0.0b12'
 
 Alternatively, after doing a complete import, these classes are available
 under the module "base":

music21/defaults.py

@@ -39,6 +39,9 @@
 # not allowing more can be construed as a feature.
 
 
+# we used to have a defaultStep ('C') and defaultOctave (4) but
+# no one ever changed them, and inlining makes so much faster.
+
 partGroup = 'Part Group'
 partGroupAbbreviation = 'PG'
 

music21/voiceLeading.py

@@ -2216,7 +2216,7 @@ def couldBePassingTone(self) -> bool:
         >>> voiceLeading.ThreeNoteLinearSegment('B##3', 'C4', 'D--4').couldBePassingTone()
         False
 
-        If no octave is given then ._defaultOctave is used.  This is generally octave 4.
+        If no octave is given then octave 4 is used:
 
         >>> voiceLeading.ThreeNoteLinearSegment('C', 'D', 'E').couldBePassingTone()
         True
@@ -2225,6 +2225,14 @@ def couldBePassingTone(self) -> bool:
         >>> voiceLeading.ThreeNoteLinearSegment('C5', 'D', 'E').couldBePassingTone()
         False
 
+        But I wouldn't skip the octave, because otherwise this will always seem baffling:
+
+        >>> voiceLeading.ThreeNoteLinearSegment('G', 'A', 'B').couldBePassingTone()
+        True
+        >>> voiceLeading.ThreeNoteLinearSegment('A', 'B', 'C').couldBePassingTone()
+        False
+
+
         Method returns True if either a chromatic passing tone or a diatonic passing
         tone is identified. Spelling of the pitch does matter!