Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Renamed the Python package to omf2. #41

Merged
merged 1 commit into from
Mar 19, 2025
Merged

Renamed the Python package to omf2. #41

merged 1 commit into from
Mar 19, 2025

Conversation

Tim-Evans-Seequent
Copy link
Collaborator

Renames the Python package to omf2 and fixes everything to work afterwards.

Using omf2 will allow it to be installed at the same time as the existing omf package for OMF v1.

robbieaverill
robbieaverill approved these changes Mar 19, 2025
View reviewed changes
Copy link

@robbieaverill robbieaverill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Do you expect this to make sense when it is merged into the upstream repo as well?

@Tim-Evans-Seequent
Copy link
Collaborator Author

LGTM. Do you expect this to make sense when it is merged into the upstream repo as well?

Yeah, it should be fine

@robbieaverill robbieaverill mentioned this pull request Mar 19, 2025
Merged
Base automatically changed from docs to main March 19, 2025 23:30
@Tim-Evans-Seequent Tim-Evans-Seequent merged commit 2b413d3 into main Mar 19, 2025
7 checks passed
@Tim-Evans-Seequent Tim-Evans-Seequent deleted the python_name branch March 19, 2025 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@robbieaverill robbieaverill robbieaverill approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Tim-Evans-Seequent @robbieaverill