The kernda from vericast

kernda's People

Contributors

Stargazers

Watchers

kernda's Issues

TIL kernda is not idempotent

If you run kernda multiple times on the same kernelspec then truly awful things happen to that poor kernelspec...

Start out with a fresh kernel:

$ python -m ipykernel install --user --name python3 --display-name "base [py3.6.5]"
Installed kernelspec python3 in /Users/edill/Library/Jupyter/kernels/python3

$ cat /Users/edill/Library/Jupyter/kernels/python3/kernel.json
{
 "argv": [
  "/Users/edill/miniconda/bin/python",
  "-m",
  "ipykernel_launcher",
  "-f",
  "{connection_file}"
 ],
 "display_name": "base [py3.6.5]",
 "language": "python"
}

So far so good. Run kernda once:

$ kernda /Users/edill/Library/Jupyter/kernels/python3/kernel.json --env-dir /Users/edill/miniconda -o
{
  "argv": [
    "bash",
    "-c",
    "source \"/Users/edill/miniconda/bin/activate\" \"/Users/edill/miniconda\" && exec /Users/edill/miniconda/bin/python -m ipykernel_launcher -f '{connection_file}' "
  ],
  "display_name": "base [py3.6.5]",
  "language": "python"
}
Wrote to /Users/edill/Library/Jupyter/kernels/python3/kernel.json

Run kernda again...

kernda /Users/edill/Library/Jupyter/kernels/python3/kernel.json --env-dir /Users/edill/miniconda -o
{
  "argv": [
    "bash",
    "-c",
    "source \"/Users/edill/miniconda/bin/activate\" \"/Users/edill/miniconda\" && exec bash -c 'source \"/Users/edill/miniconda/bin/activate\" \"/Users/edill/miniconda\" && exec /Users/edill/miniconda/bin/python -m ipykernel_launcher -f '\"'\"'{connection_file}'\"'\"' ' "
  ],
  "display_name": "base [py3.6.5]",
  "language": "python"
}
Wrote to /Users/edill/Library/Jupyter/kernels/python3/kernel.json

As of conda 4.4.0, the preferred activation strategy is to run source <PREFIX>/etc/profile.d/conda.sh followed by conda activate. The former strategy, source activate, still exists, but is being phased out. Would be good to plan similarly for kernda.