Fix typos with codespell (#2478)

CHANGES.rst

@@ -204,7 +204,7 @@ provide bug reports or feedback via: https://github.com/mu-editor/mu/issues/new
  Mu. Thank you for your patience, bug reports and code patches.
 * There have been the usual minor bug fixes and clean ups from various regular
  contributors and some new ones too. Thank you for your careful and well
- targetted changes.
+ targeted changes.
 * Carlos (@carlosperate) fixed some packaging problems relating to the iPython
  kernel bundled with Mu.
 * Martin (@dybber) fixed a couple of problems relating to the stopping of
@@ -358,7 +358,7 @@ provide bug reports or feedback via: https://github.com/mu-editor/mu/issues/new
  this is ongoing so expect further improvements in upcoming releases. As
  always, many thanks for these efforts.
 * Tim addressed a `wheel`/`sdist` related problem that was causing odd side
- effects with regard to dependancies.
+ effects with regard to dependencies.
 * A strange bug, where it was not possible to install third-party packages on
  first run of Mu, opened up a deep rabbit hole of investigation. In the end
  Tim was able to fix this AND address the source of a warning message from Qt
@@ -469,7 +469,7 @@ reports or feedback via: https://github.com/mu-editor/mu/issues/new
 * **NEW FEATURE** A brand new web mode for creating simple dynamic web
  applications with the Flask web framework. Currently users are able to edit
  Python, HTML and CSS files, run a local server and view their website in
- thier browser. We expect to add a deployment option thanks to PythonAnywhere
+ their browser. We expect to add a deployment option thanks to PythonAnywhere
  by the time alpha 3 is released.
 * **NEW FEATURE** A new Slovak translation of Mu thanks to Miroslav Biňas
  (GitHub user `bletvaska <https://github.com/bletvaska>`_).
@@ -532,7 +532,7 @@ reports or feedback via: https://github.com/mu-editor/mu/issues/new
  `Leroy Levin <https://github.com/leroyle>`_ for making this happen..!
 * Ensure that ``pip`` is updated while creating the Windows installers. Thanks
  to `Yu Wang <https://github.com/bigeyex>`_ for making this change.
-* Various minor updates and fixes to aid code readibility.
+* Various minor updates and fixes to aid code readability.
 
 1.1.0-alpha.1
 =============
@@ -804,7 +804,7 @@ next release will be 1.1.0 with some new features.
 * Update the debugger so the process stops at the end of the run.
 * Ensure the current working directory for the REPL is set to mu_mode.
 * Add additional documentation about Raspberry Pi related API.
-* Update micro:bit runtime to lates MicroPython beta.
+* Update micro:bit runtime to latest MicroPython beta.
 * Make a start on developer documentation.
 
 1.0.0.beta.11
@@ -822,7 +822,7 @@ next release will be 1.1.0 with some new features.
 * Fixed three code quality warnings found by https://lgtm.com/projects/g/mu-editor/mu/alerts/?mode=list
 * Updated API generation so the output is ordered (helps when diffing the generated files).
 * Updated Makefile to create Python packages/wheels and deploy to PyPI.
-* Explicit versions for packages found within install_requires in setup.py. 
+* Explicit versions for packages found within install_requires in setup.py.
 * Minor documentation changes.
 
 1.0.0.beta.9
@@ -875,7 +875,7 @@ next release will be 1.1.0 with some new features.
 * Change the default Python directory from ``~/python`` to ``~/mu_code``. This fixes issue #126.
 * Add instructions for installing PyQt5 and QScintilla on Mac OS.
 * Update to latest version of uFlash.
-* Add highlighting of search mathes.
+* Add highlighting of search matches.
 * Check if the script produced is > 8k.
 * Use a settings file local to the Mu executable if available.
 * Fix bug with highlighting code errors in Windows.

debian/changelog

@@ -15,7 +15,7 @@ mu (0.9.12-1) unstable; urgency=low
  * Change the default Python directory from ``~/python`` to ``~/mu_code``. This fixes issue #126.
  * Add instructions for installing PyQt5 and QScintilla on Mac OS.
  * Update to latest version of uFlash.
- * Add highlighting of search mathes.
+ * Add highlighting of search matches.
  * Check if the script produced is > 8k.
  * Use a settings file local to the Mu executable if available.
  * Fix bug with highlighting code errors in Windows.

docs/debugger.rst

@@ -14,7 +14,7 @@ standard Python, Mu does this in two ways:
  Adafruit board restarts the device and Circuit Python evaluates your
  code.
 
-Both the Python runner and grapical debugger were created with the financial
+Both the Python runner and graphical debugger were created with the financial
 support of the Raspberry Pi Foundation.
 
 If you are creating a new standard Python mode for Mu, you should *at least*
@@ -98,7 +98,7 @@ is never blocked.
 
 The ``mu.debugger.client.Debugger`` class is used to react to incoming events
 from, and as an API for Mu to issue commands to the debug runner. It uses a
-reference to a ``view`` object to update the user inteface as events are
+reference to a ``view`` object to update the user interface as events are
 detected.
 
 Debug Runner

docs/design/line-endings.rst

@@ -31,7 +31,7 @@ newline manipulation to present to the editor control the characters originally
 present in the file. When the file is saved, the same characters are written
 out.
 
-However this creates a quandary when programatically manipulating the editor
+However this creates a quandary when programmatically manipulating the editor
 text: do we use the most widespread \n as a line-ending; or do we use the
 platform convention `os.linesep`; or do we use the convention used in the
 file itself, which may or may not follow the platform convention?

docs/design/settings-and-sessions.rst

@@ -10,7 +10,7 @@ This currently uses JSON (as we have historically) but https://github.com/mu-edi
 is tracking the possibility of using TOML or some other format.
 
 Settings objects have defaults which are overridden by values loaded from file
-or set programatically. When the settings are saved, only values overriding
+or set programmatically. When the settings are saved, only values overriding
 the defaults are saved.
 
 The ``load`` method can be called several times for the same settings; values in

docs/first-steps.rst

@@ -34,7 +34,7 @@ expect certain pieces of information from you:
 
 Please try to be precise and provide as much information as possible.
 
-For what are obvious reaons, I hope you can see why we're unable to respond to
+For what are obvious reasons, I hope you can see why we're unable to respond to
 issues that say some variation of, "when I click this button, it breaks". ;-)
 
 Coding

docs/modes.rst

@@ -100,7 +100,7 @@ There are two ways to run your script in this mode:
  graphical way to inspect and watch your code execute.
 
 Because of the overhead needed to start the graphical debugger it takes longer
-to start running your script. This is especially noticable on the Raspberry Pi.
+to start running your script. This is especially noticeable on the Raspberry Pi.
 
 Python 2 isn't supported by Mu and never will be.
 
@@ -152,7 +152,7 @@ a couple of relatively simple steps:
 * In ``mu.app.py`` import the new mode from ``mu.modes`` and add an instance of
  the mode's class to the dictionary returned by the ``setup_modes`` function.
  (All modes are instantiated with the available ``editor`` and ``view``
- objects that represnt the editor's logic and UI layer respectively.)
+ objects that represent the editor's logic and UI layer respectively.)
 
 Update the Class's Behaviour
 ++++++++++++++++++++++++++++

docs/release.rst

@@ -87,7 +87,7 @@ cross platform nature of Mu is consistent):
  In", "Step Out" buttons. *Outcome: the conventional behaviour for each button
  should happen. "Stop" will stop the script. "Continue" will run to the next
  break or end of script. "Step Over" will move to the next valid line of
- code. "Step In" will move into the called funtion. "Step Out" will move out
+ code. "Step In" will move into the called function. "Step Out" will move out
  of the current function. As all this happens, the input/output pane and
  object inspector should update as the code progresses.*
 * In Python mode, click on the "REPL" button. *Outcome: an iPython based REPL

docs/setup.rst

@@ -100,7 +100,7 @@ In the setup.py file on the pyqt6 branch, you'll find the following lines::
  "PyQt6-Charts==6.3.1"
  + ';"arm" not in platform_machine and "aarch" not in platform_machine',
 
-Remove the lines for Rasberry Pi and leave only the following lines:
+Remove the lines for Raspberry Pi and leave only the following lines:
 
  "PyQt6==6.3.1",
  "PyQt6-QScintilla==2.13.3",

docs/user-experience.rst

@@ -207,7 +207,7 @@ she wants something simple and obvious.
 
 Next, she turns her attention to Idle - the editor that comes bundled with
 Python. It's good that Idle is free, has some syntax highlighting, auto-indents
-Python code, is cross platform, leightweight and simple. However, there are no
+Python code, is cross platform, lightweight and simple. However, there are no
 line numbers, error reporting is incomrehensible to beginners and, most
 importantly, there are two separate windows that often get lost or confused
 with each other (one for code, the other for a sort of REPL).

make.py

@@ -210,7 +210,7 @@ def clean():
  _rmtree(".pytest_cache")
  _rmtree("lib")
  _rmtree(".git/avatar/") # Created with `make video`
- _rmtree("venv-pup") # Created wth `make macos/win64`
+ _rmtree("venv-pup") # Created with `make macos/win64`
  # TODO: recursive __pycache__ directories
  _rmfiles(".", ".coverage")
  _rmfiles(".", "*.egg-info")
@@ -337,7 +337,7 @@ def translate_done(lang=""):
 
 @export
 def translate_test(lang=""):
- """Run translate_done and lauch Mu in the given LANG."""
+ """Run translate_done and launch Mu in the given LANG."""
  result = translate_done(lang)
  if result != 0:
  raise RuntimeError("Failed compiling the mu.po file.")

mu/debugger/runner.py

@@ -453,7 +453,7 @@ def do_quit(self):
 
  def do_close(self):
  """
- Respond to a closed socket (not a user commend, but needs handling).
+ Respond to a closed socket (not a user command, but needs handling).
  """
  self.client = None
  self.command_thread.join()

mu/interface/dialogs.py

@@ -163,7 +163,7 @@ def setup(self, envars):
  _(
  "The environment variables shown below will be "
  "set each time you run a Python 3 script.\n\n"
- "Each separate enviroment variable should be on a "
+ "Each separate environment variable should be on a "
  "new line and of the form:\nNAME=VALUE"
  )
  )

mu/interface/editor.py

@@ -85,7 +85,7 @@ class EditorPane(QsciScintilla):
  Represents the text editor.
  """
 
- # Signal fired when a script or hex is droped on this editor.
+ # Signal fired when a script or hex is dropped on this editor.
  open_file = pyqtSignal(str)
  # Signal fired when a context menu is requested.
  context_menu = pyqtSignal()
@@ -144,7 +144,7 @@ def dropEvent(self, event):
  """
 
  # Does the drag event have any urls?
- # Files are transfered as a url (by path not value)
+ # Files are transferred as a url (by path not value)
  if event.mimeData().hasUrls():
  # Qt doesn't seem to have an 'open' action,
  # this seems the most appropriate

mu/interface/main.py

@@ -292,7 +292,7 @@ def close():
  # any QWidget not just buttons
  self.tabBar().setTabButton(tab_id, QTabBar.RightSide, container)
 
- # Return the index of the new page just like the reall addTab
+ # Return the index of the new page just like the real addTab
  return tab_id
 
  def change_tab(self, tab_id):
@@ -757,7 +757,7 @@ def add_python3_runner(
  new process.
 
  If envars is given, these will become part of the environment context
- of the new chlid process.
+ of the new child process.
 
  If python_args is given, these will be passed as arguments to the
  Python runtime used to launch the child process.

mu/interface/panes.py

@@ -1359,7 +1359,7 @@ def set_start_of_current_line(self):
  Set the flag to indicate the start of the current line (used before
  waiting for input).
 
- This flag is used to discard the preceeding text in the text entry
+ This flag is used to discard the preceding text in the text entry
  field when Mu parses new input from the user (i.e. any text beyond the
  self.start_of_current_line).
  """
@@ -1588,7 +1588,7 @@ def __init__(self, parent=None):
  self.min_y = -1000
  self.flooded = False # Flag to indicate if data flooding is happening.
 
- # Holds deques for each slot of incoming data (assumes 1 to start with)
+ # Holds dequeues for each slot of incoming data (assumes 1 to start with)
  self.data = [deque([0] * self.lookback)]
  # Holds line series for each slot of incoming data (assumes 1 to start
  # with).

mu/interface/themes.py

@@ -64,7 +64,7 @@ def get_database(cls):
  """
  Create a font database and load the MU builtin fonts into it.
  This is a cached classmethod so the font files aren't re-loaded
- every time a font is refereced
+ every time a font is referenced
  """
  if cls._DATABASE is None:
  cls._DATABASE = QFontDatabase()

mu/logic.py

@@ -509,7 +509,7 @@ def __init__(self):
 
  def unexpectedError(self, filename, message):
  """
- Called if an unexpected error occured while trying to process the file
+ Called if an unexpected error occurred while trying to process the file
  called filename. The message parameter contains a description of the
  problem.
  """
@@ -691,7 +691,7 @@ def rowCount(self, parent):
  def data(self, index, role):
  """
  Reimplements QAbstractListModel.data(): returns data for the
- specified index and role. In this case only implmented for
+ specified index and role. In this case only implemented for
  ToolTipRole and DisplayRole
  """
  device = self._devices[index.row()]
@@ -1211,7 +1211,7 @@ def load_cli(self, paths):
 
  def _abspath(self, paths):
  """
- Safely convert an arrary of paths to their absolute forms and remove
+ Safely convert an array of paths to their absolute forms and remove
  duplicate items.
  """
  result = []

mu/modes/api/adafruit.py

@@ -437,10 +437,10 @@
  _("os.stat(path) \nGet the status of a file or directory.\n"),
  _("os.stat(path) \nGet the status of a file or directory.\n"),
  _(
- "os.statvfs(path) \nGet the status of a fileystem.\nReturns a tuple with the filesystem information in the following order:\n\n\nf_bsize -- file system block size\nf_frsize -- fragment size\nf_blocks -- size of fs in f_frsize units\nf_bfree -- number of free blocks\nf_bavail -- number of free blocks for unpriviliged users\nf_files -- number of inodes\nf_ffree -- number of free inodes\nf_favail -- number of free inodes for unpriviliged users\nf_flag -- mount flags\nf_namemax -- maximum filename length\n\n\nParameters related to inodes: f_files, f_ffree, f_avail\nand the f_flags parameter may return 0 as they can be unavailable\nin a port-specific implementation.\n"
+ "os.statvfs(path) \nGet the status of a filesystem.\nReturns a tuple with the filesystem information in the following order:\n\n\nf_bsize -- file system block size\nf_frsize -- fragment size\nf_blocks -- size of fs in f_frsize units\nf_bfree -- number of free blocks\nf_bavail -- number of free blocks for unprivileged users\nf_files -- number of inodes\nf_ffree -- number of free inodes\nf_favail -- number of free inodes for unprivileged users\nf_flag -- mount flags\nf_namemax -- maximum filename length\n\n\nParameters related to inodes: f_files, f_ffree, f_avail\nand the f_flags parameter may return 0 as they can be unavailable\nin a port-specific implementation.\n"
  ),
  _(
- "os.statvfs(path) \nGet the status of a fileystem.\nReturns a tuple with the filesystem information in the following order:\n\n\nf_bsize -- file system block size\nf_frsize -- fragment size\nf_blocks -- size of fs in f_frsize units\nf_bfree -- number of free blocks\nf_bavail -- number of free blocks for unpriviliged users\nf_files -- number of inodes\nf_ffree -- number of free inodes\nf_favail -- number of free inodes for unpriviliged users\nf_flag -- mount flags\nf_namemax -- maximum filename length\n\n\nParameters related to inodes: f_files, f_ffree, f_avail\nand the f_flags parameter may return 0 as they can be unavailable\nin a port-specific implementation.\n"
+ "os.statvfs(path) \nGet the status of a filesystem.\nReturns a tuple with the filesystem information in the following order:\n\n\nf_bsize -- file system block size\nf_frsize -- fragment size\nf_blocks -- size of fs in f_frsize units\nf_bfree -- number of free blocks\nf_bavail -- number of free blocks for unprivileged users\nf_files -- number of inodes\nf_ffree -- number of free inodes\nf_favail -- number of free inodes for unprivileged users\nf_flag -- mount flags\nf_namemax -- maximum filename length\n\n\nParameters related to inodes: f_files, f_ffree, f_avail\nand the f_flags parameter may return 0 as they can be unavailable\nin a port-specific implementation.\n"
  ),
  _("os.sync() \nSync all filesystems.\n"),
  _("os.sync() \nSync all filesystems.\n"),
@@ -548,7 +548,7 @@
  "random.uniform(a, b) \nReturns a random float between a and b. It may or may not be inclusive\ndepending on float rounding.\n"
  ),
  _(
- "rotaryio.IncrementalEncoder(pin_a, pin_b) \nCreate an IncrementalEncoder object associated with the given pins. It tracks the positional\nstate of an incremental rotary encoder (also known as a quadrature encoder.) Position is\nrelative to the position when the object is contructed.\n\n\nParameters:\npin_a (Pin) -- First pin to read pulses from.\npin_b (Pin) -- Second pin to read pulses from."
+ "rotaryio.IncrementalEncoder(pin_a, pin_b) \nCreate an IncrementalEncoder object associated with the given pins. It tracks the positional\nstate of an incremental rotary encoder (also known as a quadrature encoder.) Position is\nrelative to the position when the object is constructed.\n\n\nParameters:\npin_a (Pin) -- First pin to read pulses from.\npin_b (Pin) -- Second pin to read pulses from."
  ),
  _(
  "rotaryio.IncrementalEncoder.deinit() \nDeinitializes the IncrementalEncoder and releases any hardware resources for reuse.\n"

mu/modes/api/esp.py

@@ -200,7 +200,7 @@
 Create a list representing a strip of 'n' neopixels controlled from
 the specified pin (e.g. machine.Pin(0)). Use the resulting object to
 change each pixel by position (starting from 0). Individual pixels
-are given RGB (red, green, blue) values between 0-255 as a tupel. For
+are given RGB (red, green, blue) values between 0-255 as a tuple. For
 example, (255, 255, 255) is white:
 
 np = neopixel.NeoPixel(machine.Pin(0), 8)\nnp[0] = (255, 0, 128)