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

Change how we handle tertiary packages #7

Open
wrightky opened this issue Mar 15, 2021 · 1 comment
Open

Change how we handle tertiary packages #7

wrightky opened this issue Mar 15, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@wrightky
Copy link
Owner

Abandon the repeated try/except stuff inside config and opt for a local try/except inside functions which, if failed, forward the user to another script that handles unavailable packages. Could be something like:

try:
    from chord import Chord
except ImportError:
    print_install_instructions('Chord')
@wrightky wrightky added the bug Something isn't working label Mar 15, 2021
@wrightky
Copy link
Owner Author

Fixed the try/except stuff, so now we just need a good catch-all install method for packages.

Create a requirements.txt file in a fresh environment, and set it up in a script with the additional jupyter lab extension commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant