-
Notifications
You must be signed in to change notification settings - Fork 17
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
containers-run
command not recognized in venv installation on mac
#251
Comments
I am afraid that not entire mystery revealed since in the top you have
so -- datalad-container was already installed somehow, although you have not posted output from the |
Sorry for delaying this:
|
first step of troubleshooting is |
|
|
|
sorry -- damn naming discrepancy - was looking for ❯ datalad -l 1 containers-run
[DEBUG ] Command line args 1st pass for DataLad 0.19.2. Parsed: Namespace() Unparsed: ['containers-run']
[DEBUG ] Processing entrypoints
[DEBUG ] Loading entrypoint deprecated from datalad.extensions
[DEBUG ] Loaded entrypoint deprecated from datalad.extensions
[DEBUG ] Loading entrypoint container from datalad.extensions
[DEBUG ] Loaded entrypoint container from datalad.extensions
[DEBUG ] Loading entrypoint metalad from datalad.extensions
[DEBUG ] Loaded entrypoint metalad from datalad.extensions
[DEBUG ] Done processing entrypoints
[Level 5] Importing module datalad_container.containers_run
... do you see loading entry point loading for container? |
lol i didn't even spot the typo. If I fix the typo, the module is imported without error. OK, now this is weird:
I don't know if it could be because I deactivated and reactivated the environment? |
who knows... may be your shell at first didn't realize that new |
Indeed it looks like it:
so there's some base-level conda installation of datalad? If I open another shell session and activate a conda environment that has datalad installed (via pip), and then run the same command, I only see the activated environment's datalad installation:
So I guess the venv environment sees the base conda installation of datalad (first), but a conda environment sees only its only installation? |
only you would know if you did install datalad before in the
no. I think it was just a fluke of the shell that it likely used cached path to base installation . Calling |
I'm working on a mac with Python 3.9.1 base installation.
I created a fresh virtual environment using
venv
withdatalad
-core anddatalad-container
installed:Subsequently
containers-run
is not recognized:and
datalad wtf
output does not showdatalad-container
as an extension.datalad wtf
However, a
datalad rerun
command was run prior to thecontainers-run
execution, and this process internally imported modules fromdatalad-container
without problem.I then created a virtual environment with miniconda:
I then ran the
datalad containers-run -n docker-make main.pdf
command and everything worked nicely. I.e. thecontainers-run
command is recognized inside the conda environment.The text was updated successfully, but these errors were encountered: