it has always been best practice to not modify the system's python. however, to do that strictly would mean that you must do one of these:
* use python's virtualenv * install your own version of python, completely separately from the system python * install extensions to the system python using the --user option to 'pip install' none of those are particularly user-friendly. since weewx has minimal requirements, the docs use instructions that result in modification of the system's python installation. typically that mean 'sudo pip install xxx'. but on some systems you would have to first install pip, or you would have to use easy_install. i think we can continue this pattern - use the system's python - instead of complicating things for weewx users. but only if we can keep the weewx dependencies to a minimum. -- 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/37665692-184e-4087-b31a-198e618d7336%40googlegroups.com.
