Skip to content

(H001) remove deprecated OMCPath - #451

Draft
syntron wants to merge 8 commits into
OpenModelica:masterfrom
syntron:H001-remove_deprecated-OMCPath2
Draft

(H001) remove deprecated OMCPath#451
syntron wants to merge 8 commits into
OpenModelica:masterfrom
syntron:H001-remove_deprecated-OMCPath2

Conversation

@syntron

@syntron syntron commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

remove OMPathCompatibility - update needed Python version to 3.12

@syntron syntron changed the title (H001) remove deprecated OMCPath2 (H001) remove deprecated OMCPath Mar 9, 2026
@syntron
syntron force-pushed the H001-remove_deprecated-OMCPath2 branch 3 times, most recently from 3112e32 to 87df94c Compare June 30, 2026 19:50
@syntron
syntron force-pushed the H001-remove_deprecated-OMCPath2 branch 3 times, most recently from 8baf93a to 6e087fb Compare August 14, 2026 17:04
@syntron
syntron force-pushed the H001-remove_deprecated-OMCPath2 branch from 6e087fb to 3e6a378 Compare August 21, 2026 19:07
@adeas31

adeas31 commented Aug 24, 2026

Copy link
Copy Markdown
Member

How should we proceed with this?

We could release a 4.0.2 containing all the changes currently in master, then continue with the new changes. Once those are complete, we could remove the compatibility layer and make the next release 5.0.0.

What are your thoughts?

@syntron

syntron commented Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

How should we proceed with this?

We could release a 4.0.2 containing all the changes currently in master, then continue with the new changes. Once those are complete, we could remove the compatibility layer and make the next release 5.0.0.

What are your thoughts?

I'm fine with this idea; My idea is to get PR #447 and #464 in (and perhaps 1 or 2 small cleanups which are in the fork but not provided as PR). Then testing could be done in 4.0.2 (patch number increased) and - with needed cleanups - a 4.1.0 could be defined as the next intermediate release (minor number increase - compatibility with 4.x but also all new items for 5.x). The cleanup (all Hxxx items) as well as the OMParser removal (PR #472) could then be done for 5.0.0.

I will check my other open items to see if they could be closed; there is some overlap with the now merged PRs.

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.

2 participants