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

pip install of jupyterhub-samlauthenticator Does Not Install Required Dependencies #77

Open
Naveen-Annam-CMA opened this issue Jan 23, 2025 · 2 comments

Comments

@Naveen-Annam-CMA
Copy link

Title:
pip install Does Not Install Required Dependencies in Latest Release


Description:
Installing jupyterhub-samlauthenticator using pip install jupyterhub-samlauthenticator completes the installation of the package but fails to install its necessary dependencies. This results in missing dependency errors when attempting to use the package.

Steps to Reproduce:

  1. Create and activate an isolated Python environment (e.g., using venv or conda).
  2. Run pip install jupyterhub-samlauthenticator.
  3. Attempt to import the Authenticator with the command:
    from jupyterhub.auth import Authenticator
  4. Observe the error:
    ModuleNotFoundError: No module named 'jupyterhub'
    

Expected Behavior:
All required dependencies, including modules like jupyterhub.auth, should be automatically installed with the package, allowing for successful imports and usage.

Actual Behavior:
Dependencies are not installed, leading to import errors such as ModuleNotFoundError when attempting to use components like Authenticator.


Environment:

  • Python version: 3.8
  • pip version: 21.0
  • Operating System: Ubuntu 20.04

Additional Information:
This issue affects the latest release (v0.0.10) of jupyterhub-samlauthenticator. Installing the package in an isolated environment and attempting to import Authenticator results in missing module errors, indicating that dependencies were not properly installed.


Thank you!

@distortedsignal
Copy link
Contributor

Huh - interesting. I'll look into that.

There is some stuff that I need to work on RE: cleaning up 0.0.10, apparently this is one of those things.

I'm guessing it's due to Python changing its packaging format. As a temporary workaround, run a pip install of the requirements.txt file in the root of the repo.

@distortedsignal
Copy link
Contributor

Ok, I think this should be fixed on 0.0.11. @Naveen-Annam-CMA would you mind attempting to repro with 0.0.11?

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

No branches or pull requests

2 participants