Hi all, Would love to hear your views on this. I run a Python app on GAE. I have quite a few packages in my requirements.txt file, and I made the choice to not version them. Which I understand means the latest version of each requirement at the time of the project build will be used.
• Is that a crazy approach? I feel like I would not otherwise make the effort of tracking packages updates and changing versions numbers. It of course raises the issue of possible breaking change in a package update - and that happened to me already. • I'm looking for best practices on how to mitigate that. I'm using three different projects for my app: one is a dev environment, and I have a staging and production project. I would ideally like to keep requirements non-versioned in dev, but to freeze a version for staging and prod. So that I don't get into the situation where I may have validated the app in staging, then build to Prod with a significant package change. • What approach would you suggest? I'm looking for something I can automate - as I'm already using CloudBuild automation to build and deploy in staging and prod. thank you -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/d1d11711-fba6-47e2-841a-14dcf98fc8ddn%40googlegroups.com.
