On Thursday, February 23, 2017 at 1:42:16 PM UTC-5, Oliver Berger wrote: > > The key to have a distinct, reproducible setup and deployment is to use > pyenv/virtualenv
I prefer simply requiring my team using `virtualenv` and host behind a standardized nginx setup (that mimics production). That makes everything reproducible "enough". Occasionally an edge case will pop up because of slight differences in the stack, but that has most often been a good thing -- we'll have standardized the python version and packages, so we learn some random issue with other elements of the stack. We could standardize more, but that is an investment of time -- and if someone is more productive with a given setup than another, I don't want to mess with that. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/eaa3d20a-b8f1-4c02-87fb-ee09b09e80e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
