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

organize public objects and functions under launcher #2622

Closed
seanpearsonuk opened this issue Mar 26, 2024 · 0 comments · Fixed by #2628
Closed

organize public objects and functions under launcher #2622

seanpearsonuk opened this issue Mar 26, 2024 · 0 comments · Fixed by #2628
Assignees
@hpohekar
Labels
enhancement New feature or request. Feature work invariably requires testing-team involvement

Comments

@seanpearsonuk
Copy link
Collaborator

Determine what is useful to users under the launcher namespace. Make those things available directly at pyfluent.launcher. Make everything else explicitly private by prefixing with underscores.
@seanpearsonuk seanpearsonuk added the enhancement New feature or request. Feature work invariably requires testing-team involvement label Mar 26, 2024
@seanpearsonuk seanpearsonuk moved this to Prioritised in PyFluent Public Roadmap Mar 26, 2024
@hpohekar hpohekar mentioned this issue Mar 28, 2024
Merged
@github-project-automation github-project-automation bot moved this from Prioritised to In progress in PyFluent Public Roadmap Apr 2, 2024
@seanpearsonuk seanpearsonuk moved this from In progress to Done in PyFluent Public Roadmap Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hpohekar hpohekar

Labels
enhancement New feature or request. Feature work invariably requires testing-team involvement
Projects
PyFluent Public Roadmap
Status: 2021-2024
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Organize public objects and functions under launcher ansys/pyfluent
2 participants
@seanpearsonuk @hpohekar