A lightweight, multi-tenant, scalable and secure gateway that enables Jupyter Notebooks to share resources across distributed clusters such as Apache Spark, Kubernetes and others.
I'm wondering if there's any appetite for migrating from conda to venv for local development environment setup. I recently began the process in order to try tackling #1089 and I thought it might make more sense to use the Python endorsed virtual environment tool as long as we didn't need any specific conda features. It would reduce the barrier to entry for new contributions since more people might be familiar with setting up their virtual environments using that.
Proposed Solution
Rewrite requirements.yml -> requirements.txt
this could instead be left off in favor of pip install . which seems to be what jupyter_server and ipykernel suggest
update the Makefile env target to use venv rather than conda
Problem
I'm wondering if there's any appetite for migrating from conda to venv for local development environment setup. I recently began the process in order to try tackling #1089 and I thought it might make more sense to use the Python endorsed virtual environment tool as long as we didn't need any specific conda features. It would reduce the barrier to entry for new contributions since more people might be familiar with setting up their virtual environments using that.
Proposed Solution
pip install .which seems to be what jupyter_server and ipykernel suggestenvtarget to use venv rather than condaAdditional context