[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[python #OZE-274893]: Any way to avoid huuuuge git install on student machines?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [python #OZE-274893]: Any way to avoid huuuuge git install on student machines?
  • Date: Tue, 20 Feb 2018 15:42:22 -0700
Brian,

There are ways with a tool called Dask to do this kind of distributed computing 
in GitHub--but that's beyond anything I've actually done myself, and probably 
*not* for the weak of heart.

To solve your original problem with the Xcode install of git, you can use 
conda-forge to install git instead--you just need to install it in the *root* 
conda environment so that it's available when you try to create your 
environment:

conda install -n root -c conda-forge git 

Can you try that and see if it does what you'd like?

Ryan

> Hmm, perhaps we can run a jupyter-hub on our (Unidata supplied!) server…
> 
> Does that requires accounts for everyone (student notebooks stored on the 
> server)?
> 
> Or can the compute be done on the server, while the students' inputs (like 
> their USB-port measurement devices) and their results notebooks live on their 
> personal machines?
> 
> 
> Thinking aloud.
> I can hardly parse this...
> https 
> ://jupyterhub.readthedocs.io/en/latest/<https://jupyterhub.readthedocs.io/en/latest/>

Ticket Details
===================
Ticket ID: OZE-274893
Department: Support Python
Priority: Low
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.