search

pysal / giddy

Exploratory spatiotemporal data analysis and Geospatial distribution dynamics analysis
http://pysal.org/giddy/
BSD 3-Clause "New" or "Revised" License
76 stars 25 forks source link

(bug) fix environment.yml #213

Closed weikang9009 closed 6 months ago

weikang9009 commented 6 months ago

this is an attempt to fix environment.yml https://github.com/pysal/giddy/issues/209

martinfleis commented 6 months ago

Is this env meant for dev or binder? Because it won't work on binder without explicit installation of giddy.

weikang9009 commented 6 months ago

Is this env meant for dev or binder? Because it won't work on binder without explicit installation of giddy.

Do we differentiate between the two environments in PySAL packages? There does not seem to be much consistency. For instance, esda and momepy do not have themseleves in the environment file, while spopt has.

knaaptime commented 6 months ago

i dont think we have a standard convention across the library. I only use biner yamls for workshops so i just keep the generic one (with dependencies not the package itself) inside the repo

martinfleis commented 6 months ago

I was asking because the original name here was referring to binder. I don't mind, binder has been a bit hit and miss lately with geo envs. Their new 1GB RAM limit means that some (like the one I am using for teaching) won't even build there. I m fine with whichever option you pick here.