Certainly. Too many scope-increase meetings on the project from hell at 
work I guess.  Sorry if I jumped the gun :-)

Anyway, I guess I always try to think "*it it was my money funding this, 
would I invest here at this time*", because time+blood pressure are things 
we all have limited budgets for too.

So I guess I'd be interested in understanding:

   - What problems does pip solve ?   What problems does it cause ?


   - Same questions re: where things are installed to.   How does switching 
   the installed locations help/hurt the as-is ?
   

   - Does switching to pip change how painful (or not) it is to release an 
   updated distribution ?   Digitally sign them ?   Etc....
   
   - Does switching to pip alter the '*git pull ; python3 setup.py build ; 
   python3 setup.py install*' kind of use case the folks more on the 
   developer bleeding edge side tend to work ?
   

   - Does it alter anything re: extension installation tools or extension 
   structure ?

Lots of moving parts in weewx's ecosystem to think about....



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/d9870223-39e3-42ad-b8df-19aad558a035%40googlegroups.com.

Reply via email to