mpf 0.80.0.dev10__tar.gz → 0.80.0.dev12__tar.gz

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/.github/workflows/build_wheels.yml

@@ -26,6 +26,7 @@ jobs:
 
       - name: Install MPF
         run: |
+          sudo apt-get install -y libjpeg-dev
           pip install --upgrade pip setuptools wheel build
           pip install -e .
 

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/.github/workflows/prospector.yml

@@ -1,6 +1,15 @@
 name: Lint all Python files
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+      - dev
+      - 0.80.x
+  pull_request:
+    branches:
+      - dev
+      - 0.80.x
+
 
 jobs:
   prospector:
@@ -14,11 +23,11 @@ jobs:
       - name: Setup python
         uses: actions/setup-python@v4
         with:
-          # Ubuntu can't run 3.12 because Pillow dependencies.
-          python-version: 3.11
+          python-version: 3.12
 
       - name: Install MPF
         run: |
+          sudo apt-get install -y libjpeg-dev
           pip install --upgrade pip setuptools wheel build prospector
           pip install -e .
 

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/.github/workflows/run_tests.yml

@@ -1,6 +1,14 @@
 name: Test on all platforms
 
-on: [push, pull_request]
+on:
+  push:
+    branches:
+      - dev
+      - 0.80.x
+  pull_request:
+    branches:
+      - dev
+      - 0.80.x
 
 jobs:
   tests:
@@ -18,6 +26,8 @@ jobs:
           python-version: 3.12
         - os: windows-latest
           python-version: 3.13
+        - os: windows-latest
+          python-version: 3.14
 
         - os: ubuntu-latest
           python-version: "3.10"
@@ -27,6 +37,8 @@ jobs:
           python-version: 3.12
         - os: ubuntu-latest
           python-version: 3.13
+        - os: ubuntu-latest
+          python-version: 3.14
 
         - os: macos-latest
           python-version: "3.10"
@@ -36,6 +48,8 @@ jobs:
           python-version: 3.12
         - os: macos-latest
           python-version: 3.13
+        - os: macos-latest
+          python-version: 3.14
 
     steps:
       - name: Checkout MPF
@@ -46,6 +60,17 @@ jobs:
         with:
           python-version: ${{ matrix.python-version }}
 
+      - name: Install jpeg support for pillow
+        shell: bash
+        run: |
+          if [ "${{ runner.os }}" == "Windows" ]; then
+            choco install libjpeg-turbo
+          elif [ "${{ runner.os }}" == "Linux" ]; then
+            # do nothing, Linux works without additional install
+            sudo apt-get install -y libjpeg-dev
+          else #must be mac!
+            brew install libjpeg-turbo
+          fi
       - name: Install MPF
         run: |
           pip install --upgrade pip setuptools wheel build coveralls

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/AUTHORS.md

@@ -30,6 +30,7 @@ their spare time, unpaid, for the love of pinball!
  * Dave Ensminger <dave@ensadi.com>
  * Charles Duncan (nullbuilds)
  * Eric Selk <ericselk2018@gmail.com>
+ * Alex Lobascio (bosh)
  * Jerome Vivien
 
 MPF was inspired by pyprocgame which was written by:
@@ -37,4 +38,4 @@ MPF was inspired by pyprocgame which was written by:
  * Adam Preble
  * Gerry Stellenberg
 
-Want to contribute to MPF? Get started here: https://missionpinball.org/about/contributing_to_mpf/
+Want to contribute to MPF? Get started here: https://missionpinball.org/latest/about/contributing_to_mpf/

mpf-0.80.0.dev12/CONTRIBUTING.md

@@ -0,0 +1 @@
+See: https://missionpinball.org/latest/about/contributing_to_mpf/

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/PKG-INFO

@@ -1,11 +1,11 @@
 Metadata-Version: 2.4
 Name: mpf
-Version: 0.80.0.dev10
+Version: 0.80.0.dev12
 Summary: The Mission Pinball Framework (MPF)
 Author-email: The Mission Pinball Framework Team <brian@missionpinball.org>
 License: MIT
 Project-URL: homepage, https://missionpinball.org
-Project-URL: support-forum, https://missionpinball.org/community/
+Project-URL: support-forum, https://missionpinball.org/latest/community/
 Keywords: pinball
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
@@ -14,13 +14,14 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Natural Language :: English
 Classifier: Operating System :: MacOS :: MacOS X
 Classifier: Operating System :: Microsoft :: Windows
 Classifier: Operating System :: POSIX :: Linux
 Classifier: Topic :: Artistic Software
 Classifier: Topic :: Games/Entertainment :: Arcade
-Requires-Python: <3.14,>=3.10
+Requires-Python: <3.15,>=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE.md
 License-File: AUTHORS.md
@@ -34,7 +35,7 @@ Requires-Dist: ruamel.yaml==0.18.6
 Requires-Dist: setuptools~=72.2.0
 Requires-Dist: sortedcontainers==2.4.0
 Requires-Dist: terminaltables==3.1.10
-Requires-Dist: Pillow==10.4.0
+Requires-Dist: Pillow==11.3.0
 Provides-Extra: crash-reporter
 Requires-Dist: requests==2.28.2; extra == "crash-reporter"
 Provides-Extra: irc

mpf-0.80.0.dev12/RELEASE.md

@@ -0,0 +1 @@
+See: https://missionpinball.org/latest/versions/release_notes/

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/docs/code/machine_code.rst

@@ -18,7 +18,7 @@ match up to any of MPF's built in devices. The elevator and claw unloader
 in *Demolition Man* is a good example, and what we'll use here.
 
 (You can read about how to download and run *Demo Man* in the
-`example games section <https://missionpinball.org/example_games/>`_
+`example games section <https://missionpinball.org/latest/examples/>`_
 section of the MPF User Documentation.)
 
 Here's how to create a custom code class:

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/docs/dev/event_annotations.rst

@@ -25,7 +25,7 @@ document the event in code and in the docs, we use a custom docblock annotation:
     reason: The reason for this awesomeness is stated here.
   '''
 
-The event should be added to the `event reference <https://missionpinball.org/events/>`_
+The event should be added to the `event reference <https://missionpinball.org/latest/events/>`_
 on missionpinball.org.
 
 Note: As of June 2023, the events list on missionpinball.org is no longer automatically generated.

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/docs/dev/mc.widget_player.rst

@@ -42,7 +42,7 @@ So here is our base ``widget`` from the config file that we will be using.
             x: 35
 
 Refer to the widget section in the docs for more info on how to set it up:
-https://missionpinball.org/mc/widgets/
+https://missionpinball.org/latest/mc/widgets/
 
 Writing the settings to show/play this widget in code
 ^^^^^^^^^^^^^^^
@@ -69,7 +69,7 @@ When it comes to the settings we start with the following:
 
 You need to add ``action`` and ``key`` to make the ``widget`` work.
 Refer to the ``widget_player`` section for more info on these and what other functions can be added:
-https://missionpinball.org/config_players/widget_player/
+https://missionpinball.org/latest/config_players/widget_player/
 
 Now you can show the pre-defined widget from the config file.
 
@@ -107,7 +107,7 @@ The following code shows how to override an image and x-coordinate
 You can ``change``/``add`` everything this way from the related type of ``widget``, or the common settings for all widgets.
 Refer to the common settings for a overview of all settings.
 
-https://missionpinball.org/mc/widgets/common_settings/
+https://missionpinball.org/latest/mc/widgets/common_settings/
 
 Just make sure you format this way
 
@@ -127,7 +127,7 @@ Creating animation from predefined animations
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The easiest thing is to change/add pre-defined animations.
 See chapter 9 of widget animation for more info on this:
-https://missionpinball.org/mc/widgets/animation/
+https://missionpinball.org/latest/mc/widgets/animation/
 
 .. code-block:: python
 

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/docs/testing/tutorial/2.rst

@@ -1,7 +1,7 @@
 Testing Tutorial Step 2. Create your machine folder
 ===================================================
 
-`Step 2 of the MPF Tutorial <https://missionpinball.org/tutorial/2_creating_a_new_machine>`_ is where
+`Step 2 of the MPF Tutorial <https://missionpinball.org/latest/tutorial/2_creating_a_new_machine>`_ is where
 you create your machine folder and get MPF up and running with an empty config. Since it ends with MPF running and the
 attract mode being active, we can actually write a test for it!
 

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/docs/testing/writing_machine_tests.rst

@@ -25,7 +25,7 @@ your tests pass again!)
 .. rubric:: Tutorial for writing your own tests
 
 We have a complete tutorial which walks you through writing tests for your own machine. This tutorial
-conveniently follows the general MPF tutorial at `<https://missionpinball.org/tutorial>`_. Each step here matches the
+conveniently follows the general MPF tutorial at `<https://missionpinball.org/latest/tutorial>`_. Each step here matches the
 step with the same number there. (Just make sure you'll looking at the same version of the documentation
 in both places.)
 

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/mpf/_version.py

@@ -10,7 +10,7 @@ PyPI.
 
 """
 
-__version__ = '0.80.0.dev10'
+__version__ = '0.80.0.dev12'
 '''The full version of MPF.'''
 
 __short_version__ = '0.80'
@@ -19,7 +19,7 @@ __short_version__ = '0.80'
 __bcp_version__ = '1.1'
 '''The version of BCP this build of MPF uses.'''
 
-__gmc_version__ = '0.1.5'
+__gmc_version__ = '0.1.6'
 '''The version of GMC this build of MPF requires.'''
 
 __config_version__ = '6'
@@ -40,7 +40,7 @@ extended_version = "Mission Pinball Framework v{}, Config version:{}, Show versi
 '''An extended version string that includes the MPF version, show version,
 and BCP versions used in this build of MPF.'''
 
-log_url = "https://missionpinball.org/logs"
+log_url = "https://missionpinball.org/latest/logs"
 # TODO make dynamic "https://docs.missionpinball.org/en/dev/logs/{}.html"
 
 __api__ = ['version',

{mpf-0.80.0.dev10 → mpf-0.80.0.dev12}/mpf/config_players/random_event_player.py

@@ -23,48 +23,44 @@ class RandomEventPlayer(ConfigPlayer):
         """Return true if scope is not player."""
         return settings['scope'] != "player"
 
-    def _get_randomizer(self, settings, context, calling_context):
-        key = "random_{}.{}".format(context, calling_context)
-        if settings['scope'] == "player":
-            if not self.machine.game.player[key]:
-                self.machine.game.player[key] = Randomizer(
-                    settings['events'], self.machine, template_type="event")
-                r'''player_var: random_(x).(y)
+    def _build_randomizer(self, settings):
+        randomizer = Randomizer(settings['events'], self.machine, template_type="event")
+
+        if settings['force_all']:
+            randomizer.force_all = True
 
-                desc: Holds references to Randomizer settings that need to be
-                tracked on a player basis. There is nothing you need to know
-                or do with this, rather this is just FYI on what the player
-                variables that start with "random\_" are.
-                '''
+        if not settings['force_different']:
+            randomizer.force_different = False
 
-                if settings['force_all']:
-                    self.machine.game.player[key].force_all = True
+        if settings['disable_random']:
+            randomizer.disable_random = True
 
-                if not settings['force_different']:
-                    self.machine.game.player[key].force_different = False
+        randomizer.fallback_value = settings.get('fallback_event')
+        return randomizer
 
-                if settings['disable_random']:
-                    self.machine.game.player[key].disable_random = True
+    def _get_randomizer(self, settings, context, calling_context):
+        key = "random_{}.{}".format(context, calling_context)
+        if settings['scope'] == "player":
+            if not self.machine.game.player[key]:
+                self.machine.game.player[key] = self._build_randomizer(settings)
 
-                self.machine.game.player[key].fallback_value = settings.get('fallback_event')
+            '''player_var: random_(x).(y)
 
+            desc: Holds references to Randomizer settings that need to be
+            tracked on a player basis. There is nothing you need to know
+            or do with this, rather this is just FYI on what the player
+            variables that start with "random_" are.
+            '''
             return self.machine.game.player[key]
 
         if key not in self._machine_wide_dict:
-            self._machine_wide_dict[key] = Randomizer(
-                settings['events'], self.machine, template_type="event")
-
-            if settings['force_all']:
-                self._machine_wide_dict[key].force_all = True
-
-            if not settings['force_different']:
-                self._machine_wide_dict[key].force_different = False
-
-            if settings['disable_random']:
-                self._machine_wide_dict[key].disable_random = True
+            self._machine_wide_dict[key] = self._build_randomizer(settings)
 
-            self._machine_wide_dict[key].fallback_value = settings.get('fallback_event')
+        '''machine_var: random_(x).(y)
 
+        desc: Holds references to Randomizer settings that need to be
+        tracked on a machine basis.
+        '''
         return self._machine_wide_dict[key]
 
     def play(self, settings, context, calling_context, priority=0, **kwargs):