Skip to content

Conversation

@syntron
Copy link
Contributor

@syntron syntron commented Dec 29, 2025

Based on PR #400 / #402 the test matrix needs to check for different settings including a breaking change in OM;

    # test for:
    # * Python 3.10 - oldest supported version
    # * Python 3.12 - changes in OMCSession / OMCPath
    # * Python 3.14 - latest Python version
    python-version: ['3.10', '3.12', '3.14']
    # * Linux using ubuntu-latest
    # * Windows using windows-latest
    os: ['ubuntu-latest', 'windows-latest']
    # * OM 1.25.0 - before changing definition of simulation overrides
    # * OM stable - latest stable version
    # * OM nightly - latest nightly build
    omc-version: ['1.25.0', 'stable', 'nightly']
    # => total of 12 runs for each test

Pylint is recommenting to order the imports in several sections alphabetically:
(1) python standard library
(2) third party packages
(3) current package
Would it make sense to combine this code and the code in linearize() in one new function?

def _process_override_data(self, om_cmd, sim_override, file_override) -> None:
The code could:
(1) check the version; set command line parameters as needed
(2) create the content of the override file
(3) create the overwrite file and set it as command line parameter

The advantage would be, that the modified code is not in two places but only in one ...
…ons as dict[str, str]

* after OMC is run, the values will be string anyway
* simplify code / align on one common definition for these dicts
python-version: ['3.10', '3.12', '3.14']
os: ['ubuntu-latest', 'windows-latest']
omc-version: ['1.25.0', 'stable', 'nightly']
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant