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.

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

Use less unwieldy package and module names #164

Open
sajith opened this issue May 8, 2023 · 0 comments · May be fixed by #172
Open

Use less unwieldy package and module names #164

sajith opened this issue May 8, 2023 · 0 comments · May be fixed by #172

Comments

@sajith
Copy link
Member

sajith commented May 8, 2023

There are two parts to this:

  1. The package name "fabrictestbed-extensions" (and the PyPI project name) do not reflect accurately what the package does: this is is a collection of higher-level abstractions to work with FABRIC testbed, and we often call it "FABLib". Since the name fablib is already taken in PyPI, we need to think about a name: "fabrictestbed-fablib" perhaps?

  2. The current way to import FABLib is perhaps a little too unwieldy:

from fabrictestbed_extensions.fablib.fablib import FablibManager as fablib_manager

We should look into a more easier to use module arrangement, while maintaining backward compatibility.

@sajith sajith linked a pull request Jun 7, 2023 that will close this issue
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 a pull request may close this issue.

1 participant